-
Notifications
You must be signed in to change notification settings - Fork 987
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
Match the changes in collectibles api in status-go #18033
Conversation
Jenkins BuildsClick to see older builds (8)
|
[:wallet/last-collectible-details]) | ||
{:keys [id collectible-data preview-url collection-data]} collectible | ||
{:keys [traits description]} collectible-data | ||
chain-id (get-in id [:contract-id :chain-id])] |
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.
should we have a sub to access this data instead?
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.
good idea, will update it!
@@ -231,18 +232,37 @@ | |||
|
|||
(rf/reg-event-fx :wallet/store-last-collectible-details store-last-collectible-details) | |||
|
|||
(def collectible-data-types |
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.
It's very helpful during refactors to see private vars with the metadata because then we feel much safer to move things around knowing we're not missing usages. clojure-lsp helps a lot, but I don't fully trust it at all times because it's easy to get in a situation where the cache is stale while changing a lot of code.
collectibles-request-batch-size | ||
data-type | ||
fetch-criteria]] | ||
{:json-rpc/call [{:method "wallet_getOwnedCollectiblesAsync" |
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've noticed we are having trouble following the re-frame guideline for using only :db
and :fx
in the returned map (https://github.com/status-im/status-mobile/blob/develop/doc/new-guidelines.md#registering-event-handlers). A lot of events in the repo only dispatch one effect (plus maybe the :db
) so maybe we should relax that guideline. I would prefer if we had only one way of doing something and following re-frame's best practices, but it's tedious to comment in PRs to reinforce this guideline, so realistically speaking we should consider relaxing that guideline if we can't properly enforce it.
61e9240
to
e645a2a
Compare
642479b
to
3c6ebc9
Compare
fixes #17936
Summary
Collectible api was changed by this status-go PR.
This PR updates the mobile code to match the changes.
Review notes
Latest
status-go
commit used, not sure if it is better to use the commit from PR with API changes.status: ready