fix(language): accept numeric schema aliases before preprocessing#202
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 028a04611d
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| new BigDecimalNumber(value); | ||
| return true; |
There was a problem hiding this comment.
For explicit Double schema nodes with a string value outside the finite JS double range, such as value: "1e309", this branch now accepts the schema because BigDecimalNumber can parse arbitrary-size decimals. After preprocessing changes type: Double to the core blueId, BlueNode.getValue() still rounds via parseFloat and tries to construct a decimal from Infinity, so schema verification or consumers that read the value can throw later instead of rejecting the malformed schema during deserialization as before.
Useful? React with 👍 / 👎.
1 participant
No description provided.