[fix] Incorrect guess formatting #58
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
DylanDevelops
requested changes
Apr 7, 2025
Owner
DylanDevelops
left a comment
There was a problem hiding this comment.
The formatting doesn't pass our build CI/CD checks.
To fix this, run
npm run lint:fixin the console and commit the changes.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request includes changes to the
ImageGamecomponent inapp/(gameplay)/game/_components/ImageGame.tsxto improve the user experience by conditionally rendering different elements based on whether the user's guess was correct or incorrect.Improvements to user experience:
wasCorrectstate. If the guess was correct, the correct image is displayed; otherwise, the incorrect image is displayed. [1] [2]