dialect §2: drop the adapter-http query exception once Runner v0.28.0 holds query to §4.1
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- markdown
- Domain
- documentation
Research direction
Read §2 of spec/dialect.md and check whether Runner v0.28.0 has shipped. Once it has, remove the adapter-http query exception or mark it as historical; the section should state that accepted mapping v2 documents are version-2 dialect documents with no exception.
Written by the indexing model from the issue text.
Description
spec/dialect.md §2 records one exception to "a mapping v2 document the Runner accepts is a version-2 dialect document": an adapter-http request's query, which the Runner holds "to the rules of a template alone", while this document requires string templates as well (§4.1).
Runner #201 (Judgment-Pack/judgment-pack-runner#200) removes that difference. The Runner will hold an adapter-http query to §4.1, an object of string templates, and will refuse any other form as profile-mismatch. It does so at preview, at preparation, in verify-run and at workflow freeze. Once that ships in Runner v0.28.0, the exception sentence describes a Runner that no longer exists.
Change: remove the exception, or restate it as history ("before Runner v0.28.0 …"), so that §2 says a mapping v2 document the Runner accepts is a version-2 dialect document with no exception. Land it with or after the Runner release, not before.
- Dominant language
- Python
- Stars
- 5
- Forks
- 6
- Avg merge
- 6h 15m
- Merged PRs (30d)
- 98
Getting set up
- No 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 Judgment-Pack/judgment-pack-spec
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Judgment-Pack/judgment-pack-spec#275 ·
Maintainers usually reply within 1 day
-
Cover a rule's or an exception's reference list written without its array, or with a repeated entryOpengood first issue
Difficulty 2/5 Half a day Newbie friendliness 76/100
Judgment-Pack/judgment-pack-spec#158 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 8/100
Judgment-Pack/judgment-pack-spec#287 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
Judgment-Pack/judgment-pack-spec#286 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Judgment-Pack/judgment-pack-spec#284 ·
Maintainers usually reply within 1 day
All issues in Judgment-Pack/judgment-pack-spec
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
aws-samples/sample-per-model-bedrock#795 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Pretalx reports older version to be the latest release than what is actually installed and availableOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
micropython/micropython#19906 ·
Maintainers usually reply within 1 day