-
Notifications
You must be signed in to change notification settings - Fork 5
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
Add wallet connect for the new object requests #236
Conversation
8834b3e
to
00469c6
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #236 +/- ##
==========================================
- Coverage 22.08% 21.88% -0.21%
==========================================
Files 17 17
Lines 3319 3583 +264
==========================================
+ Hits 733 784 +51
- Misses 2450 2639 +189
- Partials 136 160 +24 ☔ View full report in Codecov by Sentry. |
Header parameters `X-Bearer-Signature`, `X-Bearer-Signature-Key`, and query parameters `walletConnect`, `fullBearer` were added to the new GET and HEAD object requests `/objects/{cid}/by_id/{oid}` and `/objects/{cid}/by_attribute/{oid}`. This ensures consistency of the requests using the new API, as the deprecated requests use an authorization scheme with wallet connect. Signed-off-by: Tatiana Nesterenko <[email protected]>
Signed-off-by: Tatiana Nesterenko <[email protected]>
…d `by_attribute` Signed-off-by: Tatiana Nesterenko <[email protected]>
Header parameters `X-Bearer-Signature`, `X-Bearer-Signature-Key`, and query parameters `walletConnect`, `fullBearer` were added to the new POST object requests `/objects/{cid}`. This ensures consistency of the requests using the new API, as the deprecated requests use an authorization scheme with wallet connect. Signed-off-by: Tatiana Nesterenko <[email protected]>
Signed-off-by: Tatiana Nesterenko <[email protected]>
00469c6
to
9de9307
Compare
Signed-off-by: Tatiana Nesterenko <[email protected]>
Signed-off-by: Tatiana Nesterenko <[email protected]>
9de9307
to
a4827bb
Compare
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.
So, can fullBearerToken
be avoided with autodetection? We can't avoid signature* set of parameters, but this one seems to be redundant.
Yes, I've prepared a separate branch for it, but since it's not related to this issue, I was going to push it after this branch is merged into master. |
Close #234.