DiamondLightSource / DiamondLightSource/atlas

Make read-only components more visually distinctive

Open
#146 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
1
Forks
4
Avg merge
6d 8h
Merged PRs (30d)
8

Description

For the i15-1 puck selection a component was made read-only (see discussion at https://github.com/DiamondLightSource/atlas/pull/133#discussion_r3721451891) but it's not obvious to a user that this is read-only at a glance. We should make read only components more visually distinctive

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the i15-1 puck selection and the read-only component discussed in pull request 133, especially the linked discussion. Identify where the component's visual styling is defined, then make its read-only state visibly distinct and verify the selection still renders correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
design, frontend
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.