fix: JSON export region_id type consistency#957
Merged
Conversation
dosubot
Bot
added
size:XS
pandurangareddy
approved these changes
Mar 4, 2025
pandurangareddy
left a comment
pandurangareddy
left a comment
There was a problem hiding this comment.
This code can be committed and it's out put is working.
dr5hn
approved these changes
Mar 4, 2025
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
3 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.
Fixes #956 by making sure that the 'region_id' is stored as an int (consistent with other ids and data model).
This will ensure that the region_id in the json and yaml exports of the subregions is an int.