palantir / palantir/go-java-launcher
Kebab-case YML keys
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 76
- Forks
- 29
- Avg merge
- 11h 34m
- Merged PRs (30d)
- 25
Description
Currently, YML keys are camelCase: configType, serviceName etc. We've generally been moving towards standardizing on kebab-case for YML configuration keys. Not sure if it's worth doing here as well, but opening an issue to track/discuss.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
The issue mentions YML configuration keys such as configType and serviceName, but names no file, test, or entry point. First determine where these keys are defined and consumed, then confirm the desired kebab-case convention and update all affected documentation or tests so configuration loading remains consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, yaml
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100