Start documenting code
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- documentation
Research direction
Start by inventorying the existing functions and components, then review the current instructions for running and setting up the web UI. Done means existing and newly written functions/components have docstrings and the run/setup documentation is clearer and more complete.
Written by the indexing model from the issue text.
Description
- Add docstrings to functions/components already there.
- Write new ones with docstrings.
- Document better how to run/set up/ etc...
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 1
- Avg merge
- 4h 10m
- Merged PRs (30d)
- 5
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- 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 DiamondLightSource/mx-daq-ui
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
DiamondLightSource/mx-daq-ui#153 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
DiamondLightSource/mx-daq-ui#142 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
DiamondLightSource/mx-daq-ui#140 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
DiamondLightSource/mx-daq-ui#138 ·
-
Fix snackbar behaviour for plansMay be free again @adaudon claimed this 195 days ago, and no pull request is open. Open
DiamondLightSource/mx-daq-ui#136 · 1 assignee ·
All issues in DiamondLightSource/mx-daq-ui
Similar issues
-
area/frontend area/v2 kind/bug priority/needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
kubeflow/notebooks#1498 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
P1
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
SuruchBoss/Cwork#90 ·
-
bug cli service
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
521xueweihan/HelloGitHub#3922 ·