-
Notifications
You must be signed in to change notification settings - Fork 47
chore: remove RPC for public credentials and remove Api suffix from runtime APIs
#426
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
Conversation
| pub trait ItemFilter<Item> { | ||
| fn should_include(&self, credential: &Item) -> bool; | ||
| } |
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.
there is a similar trait in Frame support(?).
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.
Are you talking about InstanceFilter ?
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.
Yes, but in the last conversation we had (#378 (comment))
we agreed we don't need any superset logic, so I would rather not use that. I would be happy to use any other trait that would work, otherwise we can keep it as it is, and get rid of it in the future if needed.
wischli
left a comment
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!
Since runtime APIs are easier to support in the SDK and to version, and because we did not do any crazy logic at the RPC layer, I think removing the RPC is a good idea. It also removes the
node-commonfolder since there is nothing in there anymore.The runtime API for
get_credentialshas also been modified from taking already a formed AssetDid (i.e., an enum), to accept aVec<u8>, and internally it tries to decode it to a validAssetDid, failing in case the input is invalid.We probably also don't need to derive
serdeanymore for most of the types, since runtime API use SCALE encoding, but I left that out and to be tackled in a separate PR, maybe even #419.