-
Notifications
You must be signed in to change notification settings - Fork 49
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
Enh/setup entity queries #2543
Enh/setup entity queries #2543
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
Caution Review failedThe pull request is closed. WalkthroughThis pull request focuses on updating the Eternum client's dependencies and refactoring several core components. The changes primarily involve incrementing versions of Changes
Suggested reviewers
Possibly related PRs
Poem
Tip CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command 📜 Recent review detailsConfiguration used: CodeRabbit UI ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (7)
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Failed to generate code suggestions for PR |
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.
The changes look good overall with nice performance optimizations and improved entity queries. The Dojo engine upgrade seems well integrated. A few suggestions:
- Consider adding a debug/development flag for performance logging to avoid unnecessary logging in production
- The commented code in World.tsx should either be removed or documented
- Consider using a proper logging utility that can be configured for different environments
- The performance measurements are a good addition but could benefit from error handling
No major issues found that would block merging.
Thanks for using MentatBot. Give comments a 👍 or 👎 to help me improve!
@@ -116,6 +117,12 @@ export const World = ({ backgroundImage }: { backgroundImage: string }) => { | |||
[structures, subscriptions], | |||
); | |||
|
|||
// const { getBuildings } = useBuildings(); |
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.
Consider removing commented out code or documenting why it's kept for future reference
@@ -126,6 +133,13 @@ | |||
return; | |||
} | |||
|
|||
// syncBuildingQty(dojo.network.toriiClient, dojo.network.contractComponents as any, structureEntityId.toString()); |
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.
Consider removing commented out code or documenting why it's kept for future reference
@@ -151,14 +198,18 @@ export async function setup({ ...config }: DojoConfig) { | |||
"s0_eternum-SwapEvent", | |||
"s0_eternum-LiquidityEvent", | |||
"s0_eternum-HyperstructureContribution", | |||
"s0_eternum-MapExplored", | |||
], | |||
}, | |||
}, | |||
false, | |||
false, |
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.
Consider wrapping performance logging in a debug flag or environment variable to avoid logging in production
false, | ||
); | ||
Promise.all([promiseTiles, promisePositions]).then(([tiles, positions]) => { | ||
console.log(tiles, positions); |
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.
Consider using a logging utility that can be configured for different environments instead of direct console.log
Summary by CodeRabbit
New Features
Bug Fixes
Documentation
Refactor
Style