Fix JSON formatting in data.nl-NL.json#12438
Merged
tdipisa merged 1 commit intoMay 28, 2026
Merged
Conversation
This was referenced May 28, 2026
tdipisa
approved these changes
May 28, 2026
tdipisa
merged commit 1b79881
into
geosolutions-it:backport-12300-to-2026.01.xx
3 checks passed
tdipisa
added a commit
that referenced
this pull request
May 29, 2026
* BACKPORT-CONFLICT * Fix JSON formatting in data.nl-NL.json (#12438) * Update data.nl-NL.json --------- Co-authored-by: ygodaert <82503232+ygodaert@users.noreply.github.com> Co-authored-by: Tobia Di Pisa <tobia.dipisa@geosolutionsgroup.com>
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.
Description
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
Issue
#12436
What is the new behavior?
Removed
"<<<<<<< HEAD
======="
Breaking change
Does this PR introduce a breaking change? (check one with "x", remove the other)
Other useful information