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: Prayers set now defaults to circlet #2519

Merged

Conversation

adnan007d
Copy link
Contributor

@adnan007d adnan007d commented Oct 24, 2024

Describe your changes

Added a function that returns flower for all sets and circlet for Prayers set
When update is triggered in ArtifactSetAutocomplete get the slotKey from the new value and return flower or circlet depending on the set

Issue or discord link

Resolves #2437

Testing/validation

Prayers defaults to Circlet
image

Other sets defaults to Flower
image

Checklist before requesting a review (leave this PR as draft if any part of this list is not done.)

  • I have commented my code in hard-to understand areas.
  • I have made corresponding changes to README or wiki.
  • For front-end changes, I have updated the corresponding English translations.
  • I have run yarn run mini-ci locally to validate format and lint.
  • If I have added a new library or app, I have updated the deployment scripts to ignore changes as needed

Summary by CodeRabbit

  • New Features

    • Enhanced artifact editing functionality with dynamic determination of default slot keys based on artifact set keys.
  • Bug Fixes

    • Improved logic for setting default slot keys, replacing the previous static assignment.

Copy link
Contributor

coderabbitai bot commented Oct 24, 2024

Walkthrough

The changes introduce a new function, getDefaultSlotKey, in the ArtifactEditor component to determine the default artifact slot key based on the artifact set key. If the artifact set begins with "Prayers", it assigns 'circlet'; otherwise, it defaults to 'flower'. This function replaces the previous static logic in the update method. The artifactReducer remains unchanged, and the overall structure of the ArtifactEditor is preserved, focusing on enhancing the logic for determining the appropriate slot key for artifacts.

Changes

File Path Change Summary
libs/gi/ui/src/components/artifact/editor/index.tsx Added function getDefaultSlotKey to determine default artifact slot key based on artifact set key. Updated update method to utilize this function.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant ArtifactEditor
    participant SlotKeyFunction

    User->>ArtifactEditor: Update artifact
    ArtifactEditor->>SlotKeyFunction: Call getDefaultSlotKey(artifactSetKey)
    SlotKeyFunction-->>ArtifactEditor: Return slotKey ('circlet' or 'flower')
    ArtifactEditor->>User: Display updated artifact with slotKey
Loading

🐇 "In the world of artifacts, a key we now find,
With 'circlet' or 'flower', our logic is kind.
From 'Prayers' it springs, a new path to take,
A hop and a jump, for the editor's sake!" 🌼✨


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 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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)
libs/gi/ui/src/components/artifact/editor/index.tsx (1)

277-281: Consider improving comment alignment.

The explanatory comment could be better aligned with the code for improved readability.

-        // 'flower' for all sets and 'circlet' for Prayers Set (Which only have circlets).
-        newValue.slotKey =
-          artifact?.slotKey ??
-          fixedSlotKey ??
-          getDefaultSlotKey(newValue.setKey)
+        // 'flower' for all sets and 'circlet' for Prayers Set (which only have circlets).
+        newValue.slotKey = artifact?.slotKey ??
+                          fixedSlotKey ??
+                          getDefaultSlotKey(newValue.setKey)
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 58e12a7 and a79151f.

📒 Files selected for processing (1)
  • libs/gi/ui/src/components/artifact/editor/index.tsx (2 hunks)
🔇 Additional comments (2)
libs/gi/ui/src/components/artifact/editor/index.tsx (2)

139-147: LGTM! Clean implementation of the default slot key logic.

The function is well-typed, pure, and correctly implements the requirement to default to 'circlet' for Prayers sets and 'flower' for others.


Line range hint 516-520: Verify handling of all Prayer set variants.

Let's ensure we're catching all Prayer set variants consistently.

✅ Verification successful

Based on the search results, I can now generate the final response since I have comprehensive information about Prayer set handling in the codebase:

Prayer set variants are properly handled throughout the codebase

The codebase consistently handles all Prayer set variants:

  • All 4 Prayer sets are properly defined and handled:
    • PrayersForDestiny
    • PrayersForIllumination
    • PrayersForWisdom
    • PrayersToSpringtime

The implementation correctly:

  • Forces 'circlet' slot for all Prayer sets via startsWith('Prayers') checks
  • Excludes Prayer sets from randomization since they only have circlet pieces
  • Properly handles Prayer sets in artifact selection UI and optimization logic
  • Maintains consistent handling across localization and asset management
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for all Prayer set references to verify consistent handling
rg -A 1 "Prayer" | grep -v "test"

Length of output: 59948

Copy link
Contributor

github-actions bot commented Oct 24, 2024

[frontend] [Thu Oct 24 21:55:15 UTC 2024] - Deployed 737e74e to https://genshin-optimizer-prs.github.io/pr/2519/frontend (Takes 3-5 minutes after this completes to be available)

[Thu Oct 24 22:51:04 UTC 2024] - Deleted deployment

Copy link
Owner

@frzyc frzyc left a comment

Choose a reason for hiding this comment

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

LGTM, thanks for the fix.

@frzyc frzyc merged commit 9d0655f into frzyc:master Oct 24, 2024
8 checks passed
@coderabbitai coderabbitai bot mentioned this pull request Nov 4, 2024
5 tasks
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.

Prayers Artifact Sets Not Working
2 participants