Fix #9916: handle Stat Query Engine integration in Visual Style Editor #9971
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
…Style Editor Description: - Handle integration thematic layer logic into visual style editor by adding cog icon into classification style rule to enable user to enter custom params - Integrate the view parameters configuration UI component in the visual style editor and showing the entered custom params above the color palette. - Write unit tests
6 tasks
…Style Editor Description: - Edit in translations + adding missing a translate
…Style Editor Description: - Edit unit test file for failure FE test
allyoucanmap
changed the title
allyoucanmap
approved these changes
Feb 29, 2024
|
@ElenaGallo please test this improvement on dev, thanks |
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.
Description
In this PR, these following points are handled:
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
What is the current behavior?
#9916
What is the new behavior?
Enable adding custom parameters into classification style rule for vector classification like using the thematic property.
The thematic property provides an array of fields where each one represents a select input, once a user selects one of this input the associated view parameter is included in the classify.json request to the SLD service.
Breaking change
Does this PR introduce a breaking change? (check one with "x", remove the other)
Other useful information
Removing the thematic layer is not implemented yet until finishing the complete review.