[1.0] Make unsupported tracing settings explicitly read-only
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- frontend, observability
Research direction
Start with src/flock/frontend/src/components/settings/TracingSettings.tsx and inspect how fixed tracing values, controls, and save feedback are rendered. Check the existing trace navigation and accessible labeling/focus behavior, then add a focused UI check for keyboard interaction and the absence of false save confirmation. Done means unsupported settings are visibly read-only and no unconfirmed configuration write is reported as successful.
Written by the indexing model from the issue text.
Description
The tracing settings UI shows fixed values and confirms saving without a persistence request, which gives operators a false success signal.
Scope
- Render unsupported settings as read-only and explain the effective configuration source.
- Remove the simulated save success and any control that implies persistence not provided by the backend.
- Keep existing trace navigation and accessible labeling/focus behavior.
Acceptance criteria
- The UI cannot report a successful configuration write without a confirmed backend operation.
- Read-only state and any unknown/effective-value limitation are visible.
- A focused UI check covers keyboard interaction and the absence of false save confirmation.
Boundaries
Implementing a new settings persistence API is outside this fix.
References
- Parent topic: #374.
- src/flock/frontend/src/components/settings/TracingSettings.tsx
- Dominant language
- Python
- Stars
- 120
- Forks
- 14
- Avg merge
- 19h 32m
- Merged PRs (30d)
- 8
Contributor 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 whiteducksoftware/flock
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
whiteducksoftware/flock#383 · 1 comment ·
-
[FEATURE] First-class Microsoft Foundry hosted agents through reusable Flock execution primitives Openenhancement
Difficulty 5/5 Over a week Newbie friendliness 30/100
whiteducksoftware/flock#455 ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
whiteducksoftware/flock#452 ·
-
documentation
Difficulty 4/5 3-5 days Newbie friendliness 55/100
whiteducksoftware/flock#451 ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
whiteducksoftware/flock#450 ·
All issues in whiteducksoftware/flock
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100