Changing the embedded screen dimensions made validation fail for the DCM screen
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Trace the validation path for embedded screens and compare how widget dimensions are currently used to identify whether a screen is unchanged. Reproduce the DCM screen failure after editing a subscreen, then verify that validation distinguishes genuinely changed dimensions from equivalent embedded screens.
Written by the indexing model from the issue text.
Description
So editing the subscreens that form other screens can cause errors while validating. Need to change how we compare dimensions of the widgets to determine if it's the same screen/or changed.
- Dominant language
- Python
- Stars
- 2
- Forks
- 1
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 4
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the 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 DiamondLightSource/techui-builder
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
DiamondLightSource/techui-builder#268 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 70/100
-
create top level screens from all controllers listed in a fascs.yaml from the id (pv_prefix) fieldOpen
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Some Schema rules are embedded in the codeMay be free again @OCopping claimed this 103 days ago, and no pull request is open. Open
DiamondLightSource/techui-builder#240 · 1 comment · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
All issues in DiamondLightSource/techui-builder
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
mikf/gallery-dl#9791 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
fossasia/eventyay#6151 · 1 comment ·
Maintainers usually reply within 1 day
-
P4: low tooling
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
jeffknupp/association#318 ·
-
azure-cost bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/GitHub-Copilot-for-Azure#3330 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
raullenchai/Rapid-MLX#4097 ·
Maintainers usually reply within 1 day