-
Notifications
You must be signed in to change notification settings - Fork 35
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
Feature/ws2 2949 locking add graphql support #205
Feature/ws2 2949 locking add graphql support #205
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great for the devtools part, but could you also update the runtime schema so that immutable fields are not present in the update inputs please?
The method generating these inputs is here: https://github.com/ceramicstudio/js-composedb/blob/main/packages/runtime/src/schema.ts#L866
I think that will also require some changes to the runtime definition to indicate what fields are immutable, here are the shared type definitions: https://github.com/ceramicstudio/js-composedb/blob/main/packages/types/src/index.ts
Let me know if you need more details or you want to sync on these changes some time!
655b51c
to
ff1588d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM other than the inherited immutable fields from the interfaces that could result in duplicate keys
Co-authored-by: Paul Le Cam <[email protected]>
Co-authored-by: Paul Le Cam <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
We have to wait for the Ceramic side to be ready, but we could start reviewing this side in the meantime. Here we add the new directive to recognize immutable fields and make sure to support parsing it.