typelevel / typelevel/sbt-typelevel
Adopt `scalac-options`
Open
Nobody has claimed this yet.
- #343 by @armanbilge — closed without merging
enhancement
- Dominant language
- Scala
- Stars
- 185
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
At the very least, I think it's a lot more organized than the sbt-typelevel-settings plugin. It's certainly more popular 😆 duplicating that effort here makes less and less sense, and there's things sbt-tpolecat gets right that are harder to fix here e.g. see https://github.com/typelevel/sbt-typelevel/pull/255.
/cc @DavidGregory084
Contributor 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.
Research direction
Start by reviewing linked pull request #343 and the referenced sbt-typelevel pull request #255. Compare the current sbt-typelevel-settings approach with sbt-tpolecat and scalac-options. Done means the project adopts the intended alternative without duplicating the existing effort.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100