-
Notifications
You must be signed in to change notification settings - Fork 0
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
expanded context implementation #31
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.
You mention some tests in the PR description. It would be nice to have them as unit tests in the codebase. You have certainly noticed how many of such are stacked at the end of this file.
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.
Can you give a chance to the type serde_json::Value::Object
and compare how it fits?
did-utils/src/didcore.rs
Outdated
|
||
#[derive(Serialize, Deserialize, Debug, Clone, PartialEq)] | ||
pub enum JsonItem { | ||
SingleString(String), |
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.
I feel like with this, the whole JsonObject
could resolve to a single String
, which is probably not the intent.
Tests are running, now the context implementation supports an object.