chore(): resolve lint warnings #2260
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
Contributor
Author
|
The remaining warning for |
jradcliff
approved these changes
Sep 29, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Address a number of linting issues, mainly of type
@typescript-eslint/no-unused-vars.For two instances
setVariantandsetCheckoutState(part of the Enhanced Ecommerce demo), the warning is occurring because the functionality is partially implemented. The features need to be revisited and implementation needs to be reevaluated more thoroughly. For now, this PR:// eslint-disable-next-line @typescript-eslint/no-unused-varscomment for each unused setter.// TODO:comment to each, explaining why the linter rule is being disabled and clarifying what feature needs to be implemented.This will clean up the lint output (which has been flagging each PR) while preserving the existing code and context for future development.