[Backport 2024.01.xx] #8871 Improve getLegendGraphic compatibility for print (#10041) #10443
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
1 task
1 task
|
The test was failing because this change was missing 278a75a#diff-f9adade1c5fe5f90a8653a2480feec27e73d07bd4b9cc12d6371fd6e8c240bacL579 |
offtherailz
approved these changes
Jun 26, 2024
|
@ElenaGallo, could you please test this on QA as soon as merged and deployed ? Thank you |
|
Test passed on QA |
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
[Backport 2024.01.xx] #8871 Improve getLegendGraphic compatibility for print (#10041)
fix #8871
Due to a mistake the previous one was targeting master branch instead of the stable one:
#10043
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
Issue
What is the current behavior?
#8871
What is the new behavior?
Breaking change
Does this PR introduce a breaking change? (check one with "x", remove the other)
Other useful information