-
Notifications
You must be signed in to change notification settings - Fork 34
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
@relationDocument
referring to an optional StreamID
yields internal server error if unset
#186
Comments
This PR should fix the underlying problem: ceramicnetwork/js-ceramic#2999 I'm not able to figure out the correct
|
@dbcfd @stbrody I'm still not able to get around this on the latest version. Has ceramicnetwork/js-ceramic#2999 been included in a composedb release yet? |
Sorry @m0ar, unfortunately the release of this has been held up by an unrelated bug that has been preventing us from making a new release of js-ceramic (you may have noticed it's been longer than usual since we've done a release). It's a major priority of the team right now to fix that bug so we can do a Ceramic release, which will include getting out this fix for optional relations. |
Makes total sense @stbrody , appreciate the context 🙏:cupcake: |
This has been solved with v0.7! 🎊 |
Description
(discussed on Discord with @dbcfd, adding here for completeness)
In our code base we have the need for optional relations, but there seems to be a bug where the API errors out if a
@relationDocument
field refers to an unsetproperty
even if both theStreamID
and theThing
is optional:The error returned from the ceramic API:
Technical Information
Since a
StreamID
field can be optional, a@relationDocument
field referencing that property must also be optional.The text was updated successfully, but these errors were encountered: