feat: implementation of multi data requests for multi feature selection #208
Conversation
This file contains hidden or 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
commit: |
|
So, this seems to be working as expected, I think the only issue right now, is that deleting a feature selection does not seem to retrigger fetching the data, only when selecting a feature it is trigerred |
lubojr
approved these changes
Jul 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 enables resquesting an endpoint multiple times and passing the merged combination of the returned data into the chart spec. It introduces
multiQueryproperty to the json schema options which can hold a schema property key or an array of keys.JSONForm example: https://github.com/GTIF-Austria/public-catalog/blob/477101a98e63b17b651e00f907ac68b8b57054e3/forms/LULUCF_form_comparison.json