-
Notifications
You must be signed in to change notification settings - Fork 176
Persist last used selections on homepage #184
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
Closed
Closed
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
a14bcec
Last used owner / repo / agent / model and task options don't always ...
ctate 48a83af
Preserve cursor agent selection on page reload
ctate d7525f0
Guard api key check against null selectedAgent
ctate bab7eb2
Store agent and model on dropdown change events
ctate 6e0b150
Revert to previous value to fix cursor agent issue
ctate 08407ae
Fix production build failure related to cursor agent follow-up
ctate File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
isAgentInitializedstate variable is created and set but never used anywhere in the component.View Details
📝 Patch Details
Analysis
Dead code: Unused
isAgentInitializedstate variable in TaskForm componentWhat fails: The
isAgentInitializedstate variable (line 164) is declared withuseState(false)but is never read anywhere in the component. It is set totruein two places (lines 238 and 246 in the mount effect) but never referenced in conditional rendering or any other logic.How to reproduce:
Result: TypeScript reports:
Expected: TypeScript compilation should succeed with no unused variable errors. State variables should either be used for their intended purpose or removed entirely.
Fix: Removed the unused state variable declaration and all calls to its setter function (
setIsAgentInitialized). The variable appeared to have been intended for gating renders during initialization but was never implemented, leaving it as pure dead code.