-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New release staging #270
New release staging #270
Conversation
The pull requests and branches should be in order now. ‘Release v/4.0.0 has been renamed to On the config code that was confusing: The API expects an array of facets under the key “f”. The config file code reconstructs this array for the new api functionality (a sub array with the parseable original facet name and the alternate name that can be used as an aggregation name). This array gets initialized in app/services/api_bridge/query.rb and put into the options hash for the api query in the |
change alternate to aggregation_name fix typos
nested bucket aggregation functionality with facet-related code sometimes code needs the format rdf.predicate[rdf.type#case_role] from config, for api queries sometimes code needs the aggregation name (i.e. case_roles) that will be in the api response
2478e29
to
2d753db
Compare
related to #284, filtering will not work without this line
7c7f2fc
to
9db98f3
Compare
I think this is redundant to #301 |
Replaces #269 (
release/4.0.0
). I cherry-picked the last 20 commits.