Add indicators and type selection to homepage #85
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dgading
force-pushed
the
goal-plan-cleanup
branch
from
c2f328b to
cf24d8b
Compare
dgading
force-pushed
the
goal-plan-cleanup
branch
from
9f114a3 to
233835f
Compare
acabouet
approved these changes
Feb 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This branch updates the search api to use an aggregated field for administration so the included indicators will also be filtered. To test, you will need to pull code, import config, run cron, and then build the frontend.
The one thing this does not do is get plans and indicators to work with the facets. I don't think that is going to be possible with our current data structure. There is no way to an aggregated field of topics from how nested everything is.