Squash commits of branch feature/write_protected_queryable_store:
- Bootstrap read-only check for queryable stores
- Use class name instead of static string
- Fix build breaker
- Log change
- Add unit tests
- Clean up
- Merge branch 'develop' into feature/write_protected_queryable_store
Squash commits of branch feature/hikari:
- Introduce HikariCP as connection pool
- Log change
- Close maintenance stores correctly
- Do not force minimum number of connections
- Log change
- Assert stores are closed correctly
... and test QueryableStoreDeletionHandler
- Fix license
- Fix unit tests
- Use constants
- Change change log
- Move hikari version to libraries
- Enhance documentation
- Use configuration for pool settings
Squash commits of branch feature/auto_increment:
- Bootstrap auto-increment key option
- Fix changelog
- Document stuff
- Fix unit test
- Documentation
- Use id generator in unit test extension
- Do not use mockito for type descriptor in tests
- Clean up
- Fix indentation
- Fix code formatting
- Clean up
Squash commits of branch bugfix/orderby-id:
- Bugfix orderby for an IdQueryField(ID)
- Add changelog for the bugfix ordering by ID field
- Add second unit test to order by name and id
The url needs to be escaped for the route component, so that
react-router can perform his matching logic.
But additionally, the components rendered within the
extension point also need the unescaped url to create further
links based on this url.
* Merge: Author and committer from request
* Squash: Author from request, committer from session
* Rebase: Rebase from original commit, committer from session
* Fast-forward: No changes, author and committer from tip
These are the four stratagies available for a merge. Each of them has a different requirement regarding who is seen as an author and who as a committer.
To properly escape branch names containing
special characters like `/` (e.g., replaced with `%2F`).
This ensures that copied links work correctly
even when branch names include special characters.
Squash commits of branch feature/hotfix-release-doc:
- Add documentation about the second build of a hotfix release
- Adjust the important note in hotfix release
Squash commits of branch dependabot/npm_and_yarn/koa-2.16.1:
- Bump koa from 2.15.4 to 2.16.1
Bumps [koa](https://github.com/koajs/koa) from 2.15.4 to 2.16.1.
- [Release notes](https://github.com/koajs/koa/releases)
- [Changelog](https://github.com/koajs/koa/blob/master/History.md)
- [Commits](https://github.com/koajs/koa/compare/2.15.4...v2.16.1)
---
updated-dependencies:
- dependency-name: koa
dependency-version: 2.16.1
dependency-type: indirect
...
- Merge pushlog_id_as_long, db connection refactoring
The changes involving a new Consumer API have been merged into the feature branch. This especially involves external sorting. Furthermore, the unit tests for CsvResource are now relying on real database connection.
Add aggregate functions and streams in queryable store
First, aggregate functions for minimum, maximum, sum and average
have been added to the queryable store API. These can be used
with the query fields, which have been enhanced for this.
Second, an additional stream like API has been added to retrieve
collections to avoid the creation of huge result objects.
- Merge branch 'develop' into dependabot/npm_and_yarn/koa-2.16.1
* Merge: Author and committer from request
* Squash: Author from request, committer from session
* Rebase: Rebase from original commit, committer from session
* Fast-forward: No changes, author and committer from tip
These are the four stratagies available for a merge. Each of them has a different requirement regarding who is seen as an author and who as a committer.
Using mockito is fine as long as one does not try to create
a huge amount of data. In this case it might happen, that
mockito needs a lot of memory (probably to track single
calls to methods) and in doing so might spoil load tests
and such.
Besides the endpoint, another API was added, the ShouldRequestPassChecker.
This api should be used to check whether a REST Request should be passed or rejected.
With this the queryable unit test extension
(QueryableStoreExtension) uses the same jackson mapper
configuration as in production.
In contrast to edaffc1662
where the XML annotation introspector had been missing,
now this really should be the case.
Squash commits of branch feature/uniform_configuration_document_titles:
- Use uniform document titles in configuration pages
- Use different titles for global, repository and namespace config
- Make the code a lot prettier
- Remove detailed configuration title
With this, gradle can determine the originating element for the
generated query types and the store factories correctly and
therefor can run incremental builds when the queryable type
annotation processor is added as a dependency.
