Skip to content

refactor: use geist txn table#11

Open
metalboyrick wants to merge 2 commits into
mainfrom
refactor/use-geist-txn-table
Open

refactor: use geist txn table#11
metalboyrick wants to merge 2 commits into
mainfrom
refactor/use-geist-txn-table

Conversation

@metalboyrick
Copy link
Copy Markdown
Member

No description provided.

...(method && { method }),
...(type && { type: type.join(",") }),
});
const endpoint = `https://base-sepolia.blockscout.com/api/v2/transactions?${queryString.toString()}`;
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for changes in this dmeo repo is relatives fine, but if we are able to get wagmi working, we should use tanstack query to avoid setIsLoading ?

for contributing back to upstream (geist dapp kit),

  1. I think it is hard to share same abstraction of params across data sources. e.g. here filter is not use by alchemy.

sharing txn object parsed from their responses might work to certain extent

fundamentally we might want totally separate hooks, e.g.
in wagmi we have watchContractEvent and watchAccount

Lets add type to indiciate too

  1. lets create / use existing util for blockscout endpoint on L66

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

setIsLoading was a quick fix haha for the hack.

fundamentally we might want totally separate hooks, e.g.
in wagmi we have watchContractEvent and watchAccount

You mean hooks by data provider?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants