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.
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.
The previous keyboard iterator did not take into account, if multiple items deregistered at once.
Therefore, the keyboard iterator ran into an iterator invalidation bug, because the assigned index of an element can run out of bounds.
Elements with an out of bounds assigned index, would not be able to deregister and therefore stay in the list of registered items.
Therefore messing up the iteration logic.
This adds the new "queryable store" API, that allows complex
queries and is backed by SQLite. This new API can be used
for entities annotated with the new QueryableType annotation.
Tasks.documentation.javadoc threw around 50 errors due to multiple inconsistencies within the javadoc comments.
Furthermore, the option 'failOnError' is now set to 'true' so that future Javadoc errors in our codebase are avoided.
