Frontend cleanup follow-ups from PR #369
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript, python
- Domain
- frontend
Research direction
Start with frontend/src/pages/aiSettings/index.js to inspect the two Save buttons and their handleSave behavior in Vertex mode. For the lint cleanup, locate the reverted changes from PR #369 (commit af11409, reverted by 17dbea2) and review hook dependency changes for behavior effects, including the AIChatPanel countdown example. Done when the cleanup is reapplied safely and the redundant button is hidden or has distinct behavior.
Written by the indexing model from the issue text.
Description
Frontend follow-ups from PR #369.
1. Reapply the lint cleanup
PR #369 originally included a frontend lint cleanup in about 22 files (unused imports and hook dependency changes, from af11409). It was reverted in 17dbea2 to keep #369 limited to the Vertex work.
Reapply it as its own PR and check each hook dependency change for behavior changes. For example, the AIChatPanel change made the countdown interval get recreated on every tick, so it should keep [countdown > 0] or be restructured.
2. Redundant Save Settings button on AI Settings in Vertex mode
On the AI Settings page in Vertex mode, "Save Settings" and "Save Course Default" both call handleSave (frontend/src/pages/aiSettings/index.js). Hide the first button when Vertex is selected, or give each button its own behavior.
- Dominant language
- Python
- Stars
- 13
- Forks
- 0
- Avg merge
- 2h 4m
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from kiat/codeAssist
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
kiat/codeAssist#391 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
kiat/codeAssist#364 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 63/100
kiat/codeAssist#392 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
kiat/codeAssist#389 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
kiat/codeAssist#388 ·
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
gradio-app/gradio#13964 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 93/100
BSData/horus-heresy-3rd-edition#3232 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
jbacalso24/mimry#123 ·
Maintainers usually reply within 1 day
-
p:3-mid pydanty:bug pydanty:is-working
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
pydantic/pydantic-ai#10153 · 1 comment ·
Maintainers usually reply within 1 day
-
good first issue priority: medium size: S testing
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
cubrid-lab/cubrid-cookbook-python#316 ·
Maintainers usually reply within 1 day