-
-
Notifications
You must be signed in to change notification settings - Fork 28
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
Pagination, Eslint & Context refactor #38
base: main
Are you sure you want to change the base?
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.
Thank you very much for this PR! We're in good track. I left several comments.
- This looks more like 3 PRs (Pagination, Eslit, Context refactor), please send three separate ones next time
- The build is not passing:
9:33:10 AM: Error occurred prerendering page "/Home". Read more: https://nextjs.org/docs/messages/prerender-error
9:33:10 AM: Error: useBundleData must be used within a BundleDataProvider
9:33:10 AM: at useBundleData (/opt/build/repo/.next/server/chunks/952.js:202:11)
Co-authored-by: Martín Triay <[email protected]>
Co-authored-by: Martín Triay <[email protected]>
Co-authored-by: Martín Triay <[email protected]>
Co-authored-by: Martín Triay <[email protected]>
Co-authored-by: Martín Triay <[email protected]>
Co-authored-by: Martín Triay <[email protected]>
Co-authored-by: Martín Triay <[email protected]>
Co-authored-by: Martín Triay <[email protected]>
Co-authored-by: Martín Triay <[email protected]>
Co-authored-by: Martín Triay <[email protected]>
There seems to be an issue between the CSS being served when running There are tailwind classes that aren't being included in the build css despite being used in the markup, I suspect that tailwind might have a treeshaking build step that might be missing the additional modules though still need to validate that |
closes #7
This PR additionally refactors business logic into two context hooks, one pertaining to Bundles & Tokens
The idea is that since bundles are clusters of blocks, token flow data & any nested block related data, that it would be managed there.
Consuming or interpreting transactions, tokens, balances or balance related events would be managed in the tokens context
Additionally components have been broken out into smaller
.tsx
components.To make better use of the context hook data being accessable throughout the app, a move towards TS interfaces for data has been made.Functionally nothing has changed other than some logic for sniffing out if there are more bundles to paginate through
Improvement notes
A simple, can next page, approach has been taken but loading multiple pages and reducing calls can be improved from here