Allow to specify `named-values` **in addition** to `allowed-values` for `enum` types
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- github-actions, kotlin
- Domain
- backend-api-design
Research direction
No files or tests are named. Start by locating the enum handling and JAR binding-generation entry points, then trace how allowed-values become generated constants. Done means supporting named-values alongside allowed-values, including mixed named and unnamed entries, without duplicate generated names or compilation failures.
Written by the indexing model from the issue text.
Description
Currently we only generate constant values for enums from their content.
If you have quite long or awkward possible values like the terms of use URL of the setup-gradle action, the names are a bit unhandy.
Additionally, if you have an enum with values that calculate to the same name like
inputs:
some-enum:
type: enum
allowed-values:
- foo-bar
- foo_bar
which both evaluate to FooBar, you get a 500 internal server error as soon as you request the JAR, because a compile error will happen when trying to compile the bindings.
The latter could maybe also be solved by some logic to make the names unique,
but it could also be solved by this feature request which means, that you can give explicit names for enum values.
I think it makes sense to allow unnamed and named in the same element.
- Dominant language
- Kotlin
- Stars
- 69
- Forks
- 4
- Avg merge
- 15h 16m
- Merged PRs (30d)
- 4
Getting set up
- 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 typesafegithub/github-actions-typing
-
Difficulty 5/5 Over a week Newbie friendliness 28/100
typesafegithub/github-actions-typing#205 · 1 reaction ·
-
Add typing: pairOpen
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Dependency DashboardOpen
Difficulty 1/5 Under an hour Newbie friendliness 15/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 15/100
typesafegithub/github-actions-typing#17 · 1 reaction ·
All issues in typesafegithub/github-actions-typing
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
fwcd/tree-sitter-kotlin#289 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
navikt/syfo-oppfolgingsplan-backend#482 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
MorphiaOrg/morphia#4332 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
ooni/probe-multiplatform#1614 · 1 comment ·
Maintainers usually reply within 1 day