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

context update should not require name #9

Open
sirpy opened this issue Oct 3, 2023 · 3 comments
Open

context update should not require name #9

sirpy opened this issue Oct 3, 2023 · 3 comments

Comments

@sirpy
Copy link

sirpy commented Oct 3, 2023

When trying to update a context access rules if you do not supply the name field the update request will fail.

@donatandelic
Copy link

This is expected/correct behavior, since Context's schema defines name as a non-nullable field.

You can check the latest Context schema commit on Cerscan.

@sirpy
Copy link
Author

sirpy commented Oct 3, 2023

@donatandelic so when i do context update i need to pass all the previous fields values other wise they are going to be nullified?

@donatandelic
Copy link

@sirpy That's correct. You're updating the Ceramic stream directly, so whatever content you post as a part of the update will be treated as a new (fresh) commit. The chain will not try to amend or assume changes.

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

No branches or pull requests

2 participants