Update docs for v0.7 #212
Open
Update docs for v0.7 #212
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
m0ar
reviewed
Mar 8, 2024
m0ar
left a comment
m0ar
left a comment
There was a problem hiding this comment.
Psst, missing information about the @immutableFields directive in the schema definition language. Seems it's only mentioned in the devtools 👼
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Mostly docs fixes and generated APIs updates, the main content change is about the directives to add the
SETaccount relation and theaccountRelationFields.A small functional change as well is defaulting the
shouldIndextotruewhen calling theset<Model>mutations, so unless theshouldIndexoption is explicitly set tofalse, the document should be indexed, I think this behavior would better match the expectations.