Make string key access fallback to atom key access #1
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 of the change
With this change
Simple.Json.write
andSimple.Json.read
works round-trip. Without this change, it always encodes record keys as atoms, and it always reads record keys by string, so all record accesses fail. It feels like a safe default to first check exactly what was asked for, and then fall back to atom access. Also, it's unlikely that we'll do record accesses on user input field names, so atom leaks should not be an issue.Details
Json works fine
but foreign doesn't work:
until I made the change in the pr, and then it works fine
Checklist: