fix: filter lookupOptions by current value (MAPCO-5661)#549
Merged
Conversation
Dorin-RFL
changed the title
alebinson
previously approved these changes
Dec 5, 2024
alebinson
dismissed
their stale review
too general change, should be specific
…ter resolution degrees options
…ter resolution degrees options
alebinson
approved these changes
Dec 16, 2024
| enhanced> | ||
| { | ||
| lookupOptions.map(({ translationCode, value, properties }, index) => { | ||
| lookupOptions.filter((option)=> value && option.properties.resolutionDeg as unknown as number >= Number(value)) |
Collaborator
There was a problem hiding this comment.
it's too low level, this change will be performed for all instances of this component, should be done only for specific place
This was referenced May 7, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
No description provided.