We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There is a question if crypto/verify should be doing JSON parsing, or if that should be handled separately.
Once some additional changes in fluree/server land, including how it is used in middleware, it can be examined.
I think at this point the way it is working currently is OK.
The text was updated successfully, but these errors were encountered:
Also to point out - this function is only used internally, so whatever choice is decided it will not affect anything touching end users.
Sorry, something went wrong.
No branches or pull requests
There is a question if crypto/verify should be doing JSON parsing, or if that should be handled separately.
Once some additional changes in fluree/server land, including how it is used in middleware, it can be examined.
I think at this point the way it is working currently is OK.
The text was updated successfully, but these errors were encountered: