Skip to content
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

fix mine balance max cap #2548

Merged
merged 1 commit into from
Dec 17, 2024
Merged

fix mine balance max cap #2548

merged 1 commit into from
Dec 17, 2024

Conversation

bob0005
Copy link
Collaborator

@bob0005 bob0005 commented Dec 17, 2024

Summary by CodeRabbit

  • New Features

    • Enhanced EntityResourceTable component to retrieve and utilize structure information based on entityId.
    • Updated logic for calculating maximum storehouse capacity, allowing certain structures to handle unlimited quantities.
  • Bug Fixes

    • Improved control flow for capacity calculations based on structure categories.

Copy link

vercel bot commented Dec 17, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
eternum 🔄 Building (Inspect) Visit Preview 💬 Add feedback Dec 17, 2024 7:28am
eternum-docs 🔄 Building (Inspect) Visit Preview 💬 Add feedback Dec 17, 2024 7:28am
1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
eternum-landing ⬜️ Ignored (Inspect) Visit Preview Dec 17, 2024 7:28am

Copy link
Contributor

coderabbitai bot commented Dec 17, 2024

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request modifies the EntityResourceTable component in the client's source code. The changes introduce a new method to retrieve structure information using useStructures hook and enhance the logic for calculating maximum storehouse capacity. Specifically, for structures with the FragmentMine category, the maximum capacity is set to Infinity, allowing unlimited resource storage for these specific structure types.

Changes

File Change Summary
client/src/ui/components/resources/EntityResourceTable.tsx - Added useStructures import
- Implemented structure retrieval using getStructureByEntityId
- Updated maxStorehouseCapacityKg calculation to handle FragmentMine structures with Infinity capacity

Sequence Diagram

sequenceDiagram
    participant Component as EntityResourceTable
    participant Hook as useStructures
    participant Type as StructureType

    Component->>Hook: getStructureByEntityId(entityId)
    Hook-->>Component: Return structure details
    Component->>Type: Check structure category
    alt Is FragmentMine
        Component->>Component: Set maxStorehouseCapacityKg to Infinity
    else Other structure types
        Component->>Component: Calculate standard capacity
    end
Loading

Possibly related PRs

Poem

🐰 In the realm of bits and bytes so bright,
A mine of fragments takes infinite flight!
Capacity unbounded, resources galore,
Our code dances with logic at its core.
Infinity whispers, structures rejoice! 🚀


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 93bfe50 and 9d2794d.

📒 Files selected for processing (1)
  • client/src/ui/components/resources/EntityResourceTable.tsx (2 hunks)

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?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@ponderingdemocritus ponderingdemocritus merged commit 7e4dbf8 into next Dec 17, 2024
4 of 9 checks passed
@ponderingdemocritus ponderingdemocritus deleted the fix/mine-max-balance branch December 17, 2024 07:29
Copy link
Contributor

@mentatbot mentatbot bot left a 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 and implement the Fragment Mine special case correctly. The code is well integrated with existing patterns and hooks. Just a couple of minor suggestions around documentation and dependency tracking.

Thanks for using MentatBot. Give comments a 👍 or 👎 to help me improve!

@@ -18,7 +19,11 @@ export const EntityResourceTable = ({ entityId }: { entityId: ID | undefined })
getEntityIdFromKeys([BigInt(entityId || 0), BigInt(BuildingType.Storehouse)]),
)?.value || 0;

const { getStructureByEntityId } = useStructures();
const structure = getStructureByEntityId(entityId || 0);

const maxStorehouseCapacityKg = useMemo(() => {
Copy link
Contributor

Choose a reason for hiding this comment

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

Consider adding a comment explaining why Fragment Mines have infinite storage capacity for future maintainers. This special case might not be immediately obvious to someone new to the codebase.

Suggested change
const maxStorehouseCapacityKg = useMemo(() => {
const maxStorehouseCapacityKg = useMemo(() => {
// Fragment Mines have unlimited storage capacity since they are the primary resource generation structures

const maxStorehouseCapacityKg = useMemo(() => {
if (structure?.category === StructureType[StructureType.FragmentMine]) return Infinity;
const storehouseCapacityKg = gramToKg(configManager.getCapacityConfig(CapacityConfigCategory.Storehouse));
return multiplyByPrecision(quantity * storehouseCapacityKg + storehouseCapacityKg);
}, [quantity, entityId]);
Copy link
Contributor

Choose a reason for hiding this comment

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

The useMemo dependency array should include structure since it's used in the calculation. Without it, changes to structure won't trigger a recalculation.

Suggested change
}, [quantity, entityId]);
}, [quantity, entityId, structure]);

Copy link

Failed to generate code suggestions for PR

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