Comments do not appear alongside the standard name definitions in either Metadata file
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
Research direction
Start with write_standard_name_table.py and inspect how standard_names.xml entries are read and written to each Metadata file. Verify the generated definitions include the XML comment field when it is present, while preserving entries without comments.
Written by the indexing model from the issue text.
Description
There should be an additional "comment" field when provided in standard_names.xml, but it is not being written by the current version of "write_standard_name_table.py"
- Dominant language
- Python
- Stars
- 9
- Forks
- 17
- Avg merge
- 16d 22m
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- Has a 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 ESCOMP/ESMStandardNames
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ESCOMP/ESMStandardNames#160 ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
ESCOMP/ESMStandardNames#163 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 56/100
ESCOMP/ESMStandardNames#161 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
ESCOMP/ESMStandardNames#146 ·
-
Mapping to Grib TablesMay be free again @climbfuji claimed this 171 days ago, and no pull request is open. Open
ESCOMP/ESMStandardNames#120 · 2 comments · 1 assignee ·
All issues in ESCOMP/ESMStandardNames
Similar issues
-
README.zh-CN/ja/es still hard-code 501 test counts after README.md went count-freePossibly taken @Aaqibhafeezkhan claimed this today. Openbeginner documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
BistaDinesh03/critique#164 · 1 comment ·
Maintainers usually reply within 1 day
-
bug IO
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
MrNeRF/LichtFeld-Studio#3824 ·
Maintainers usually reply within 1 day
-
bug confirmed issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
open-webui/open-webui#33200 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
The changelog workflow excludes otelbot but not dependabot, so every Dependabot pull request fails the changelog checkPossibly taken @ocelotl claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 82/100
open-telemetry/opentelemetry-python#5825 ·
Maintainers usually reply within 2 days