Yolo fix all lint warnings and errors #3
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
AI experience report: Both Cursor and Claude did a decent initial job to fix the issues, but they both broke the Canvas, Chess and Dynamic demos in the process.
In the end, Claude did a much better job as Cursor also broke the visual elements on the Canvas demo due to its refactor to remove duplicate methods (which both introduced while trying to silence the warnings).
It would be nice if there were some kind of tool that opened a web browser, and validated that all the pages work fine. Imagine running this as an automated check against this PR and discovering that the demos were not rendering! That would be amazing, wouldn't it?
#yolo