Make `publishingType` more typesafe
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Kotlin
- Stars
- 131
- Forks
- 10
- Avg merge
- 2h 5m
- Merged PRs (30d)
- 6
Description
Use sealed classes/interfaces instead of a String.
See https://github.com/GradleUp/nmcp/pull/169#discussion_r2284616608 for more details.
API compatibility and migration path TBD.
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
Start with the publishingType references and the discussion in pull request 169, especially the linked comment. Determine the required API compatibility and migration path before changing the String representation. Done means the replacement is typesafe and the compatibility and migration decisions are documented and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100