Skip to content
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

Closed
wants to merge 57 commits into from
Closed

New release staging #270

wants to merge 57 commits into from

Conversation

wkdewey
Copy link
Contributor

@wkdewey wkdewey commented Nov 21, 2022

Replaces #269 (release/4.0.0). I cherry-picked the last 20 commits.

@wkdewey
Copy link
Contributor Author

wkdewey commented Nov 22, 2022

The pull requests and branches should be in order now. ‘Release v/4.0.0 has been renamed to new_release_staging. My other branches have been rebased or cherry picked on top of that one. These changes resulted in several PR’s being closed (since they were based on the closed branch). I created new PR’s and linked to the old ones. Especially #269 which had some commentary. The order is new_release_staging -> rails6 -> rails6_ruby3 -> deep_faceting -> new_release_documentation

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 prepare_options method. I don't think a hash can substitue for my [original_facet, aggregation_name] subarray. I will make more documentation in the code.

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
@wkdewey wkdewey linked an issue Jun 1, 2023 that may be closed by this pull request
2 tasks
@wkdewey wkdewey linked an issue Jan 8, 2024 that may be closed by this pull request
@wkdewey
Copy link
Contributor Author

wkdewey commented Aug 21, 2024

I think this is redundant to #301

@wkdewey wkdewey closed this Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Labels on summary boxes Fix search interface metadata and API schema Documentation for latest release
1 participant