Visibility limits - The resolution option is not retained as Limits type #10391
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
…s/VisibilityLimitsForm.jsx
1 task
tdipisa
requested review from
dsuren1
and removed request for
offtherailz and
tdipisa
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
This PR fixes the limitsType persistence in client/components/TOC/fragments/settings/VisibilityLimitsForm.jsx. User-set settings for scale / resolution on an individual layer will now be saved across time.
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?
#10355
What is the new behavior?
Resolution / scale settings are persisted on a layer individual basis.
Breaking change
Does this PR introduce a breaking change? (check one with "x", remove the other)
Other useful information