i18next-conv@14.0.0 and p-from-callback@1.0.1 are MIT licensed according
to there License files.
Also remove po2json from the exclude list, we don't seem to use that
anymore.
* enhancement: add more kql spec tests and simplify ast normalization
* enhancement: kql parser error if query starts with AND
* enhancement: add kql docs and support for date and time only dateTimeRestriction queries
* enhancement: add the ability to decide how kql nodes get connected
connecting nodes (with edges) seem straight forward when not using group, the default connection for nodes with the same node is always OR. THis only applies for first level nodes, for grouped nodes it is defined differently. The KQL docs are saying, nodes inside a grouped node, with the same key are connected by a AND edge.
* enhancement: explicit error handling for falsy group nodes and queries with leading binary operator
* enhancement: use optimized grammar for kql parser and toolify pigeon
* enhancement: simplify error handling
* fix: kql implicit 'AND' and 'OR' follows the ms html spec instead of the pdf spec
* enhancement: add support for natural language kql date queries
* enhancement: structure kql parser tests into logical clusters
* fix: time-range error naming
* making helper function, checking and setting response in given step and when steo respectively
* returning response and using in given/then steps as required in favoritesContext
* set the returned response on SpaceContext
* changed to inline variable in some lines as required
* to check for the specific https response code
* enhancement: add more kql spec tests and simplify ast normalization
* enhancement: kql parser error if query starts with AND
* enhancement: add kql docs and support for date and time only dateTimeRestriction queries
* enhancement: add the ability to decide how kql nodes get connected
connecting nodes (with edges) seem straight forward when not using group, the default connection for nodes with the same node is always OR. THis only applies for first level nodes, for grouped nodes it is defined differently. The KQL docs are saying, nodes inside a grouped node, with the same key are connected by a AND edge.
* enhancement: explicit error handling for falsy group nodes and queries with leading binary operator
* enhancement: use optimized grammar for kql parser and toolify pigeon
* enhancement: simplify error handling
* fix: kql implicit 'AND' and 'OR' follows the ms html spec instead of the pdf spec
* migrating set response from helper function to when step in preview feature
* separate single when/then steps by converting to helper function
* use of httpstatuscode check function in given step and rebased
* change function name
* remove use of setresponse in then step
* set the returned response
* give graph driveItems some love
Signed-off-by: Jörn Friedrich Dreyer <jfd@butonic.de>
* extract parseIDParam()
Signed-off-by: Jörn Friedrich Dreyer <jfd@butonic.de>
* add GetDriveItem(Children) tests
Signed-off-by: Jörn Friedrich Dreyer <jfd@butonic.de>
---------
Signed-off-by: Jörn Friedrich Dreyer <jfd@butonic.de>
This gets us a rid of the need to configure the reva jwt secret in the
proxy. Also we no longer need to fake an internal admin user for
autoprovsioning user and/or assigning the roles to users from oidc
claims.
Ralf Haferkamp