This repository has been archived by the owner on Jan 15, 2021. It is now read-only.
Fix invalid JSON caused by localized decimal mark #130
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.
As mentioned in #123 TimeSpanConverter produced wrongly formatted (non JSON) floating point numbers on systems with comma (or any other decimal mark) instead of dot causing the Glimpse HUD not showing at all as $.getJson doesn't return without error.
The produced JSON on a system with comma as seperator before this PR looked like this:
After this PR the json will look like this: