fix non-string properties not visible in the raw tag editor#11636
Merged
fix non-string properties not visible in the raw tag editor#11636
Conversation
1ec5
reviewed
Dec 3, 2025
k-yle
force-pushed
the
kh/non-string-properties
branch
from
aeb677c to
07d0005
Compare
k-yle
force-pushed
the
kh/non-string-properties
branch
from
07d0005 to
2a11b5d
Compare
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.
If you load a gpx/geojson/mvt file via the Custom Map Data pane, only string properties work. Numbers/booleans/arrays/objects don't work.