Skip to content
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

docs: clarify lf <-> json spec #14025

Merged
merged 2 commits into from
May 31, 2022
Merged

Conversation

garyverhaegen-da
Copy link
Contributor

Trying to summarize a discussion we had on Slack.

CHANGELOG_BEGIN
CHANGELOG_END

Trying to summarize a discussion we had on Slack.

CHANGELOG_BEGIN
CHANGELOG_END
@garyverhaegen-da garyverhaegen-da force-pushed the type-directed-parsing-json branch from 75fd367 to 0542588 Compare May 31, 2022 11:47
below. **For that reason, the HTTP JSON API Service uses ``true`` for both flags.**

Type-directed Parsing
*********************

Note that throughout the document the decoding is type-directed. In
other words, the same JSON value can correspond to many Daml-LF values,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could also say here, "and vice versa: a Daml-LF value can correspond to two or more JSON encodings"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point, that'd reinforce the next paragraph.

@garyverhaegen-da garyverhaegen-da enabled auto-merge (squash) May 31, 2022 12:21
@garyverhaegen-da garyverhaegen-da merged commit a48640e into main May 31, 2022
@garyverhaegen-da garyverhaegen-da deleted the type-directed-parsing-json branch May 31, 2022 12:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants