Configure which columns are visible
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start by locating the frontend entry point that renders the aggregated log columns and identify how the date, application, and other columns are defined. Add an accessible box or dialog for changing column visibility, then verify that the selected columns are shown or hidden in the log view.
Written by the indexing model from the issue text.
Description
As a user I would like to configure which columns are and are not visible to reduce clutter that I don't care about
Acceptance Criteria
- There is some box or dialog I can access
- I can use it to change which columns (date, application etc.) are visible
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 DiamondLightSource/logpanel
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
Display Version Open
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Unit Tests Open
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
Devcontainer Openenhancement
Difficulty 3/5 1-2 days Newbie friendliness 52/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
DiamondLightSource/logpanel#46 · 1 comment ·
All issues in DiamondLightSource/logpanel
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
fullcalendar/fullcalendar#8106 ·