-
Notifications
You must be signed in to change notification settings - Fork 16
[GS] Multiple fixes and improvements for gama-server #691
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Introduces new preferences to control how #infinity, #nan, and integer overflows are written and parsed in JSON (as strings or literals). Updates JSON parsing and formatting logic to respect these preferences, adds constants for NaN and Infinity, and improves handling of special float values in JSON serialization and deserialization.
|
I've added a unit test model for to_json/from_json and taking into account the new Infinity and NaN cases, it seems like we are not here yet, some of those cases do not work |
|
What fails ? |
|
You can check by running the new Fails, but if I write this simple model: I have this output: What is even stranger is that if I change |
…n and the option is set to string
…ded by double quotes
…nfinity/nan parsing
Pull request that attempts to provide solutions for the "last" gama-server issues (#484 , #566, #619, gama-platform/gama.clients#20, maybe others?)
If it is accepted, the following changes to the documentation should also be done (to complete):
activateanddescribethe description of the returned errors should be addedurifield in the error result ofloadcommand (andactivate/describe)