Kitchen Sink import
Open
Nobody has claimed this yet.
question
- Dominant language
- Scala
- Stars
- 101
- Forks
- 9
- Avg merge
- 13m
- Merged PRs (30d)
- 1
Description
A common complaint is about the enormous amount of imports it takes to do stuff. e.g. https://github.com/http4s/http4s/discussions/6696
What if ... we just exported a bunch of useful stuff under a single package?
package typelevel.toolkit
export cats.*
export cats.effect.*
export fs2.*
export org.http4s.*
export org.http4s.ember.client.EmberClientBuilder
// etc.
Not gonna lie, it's playing with fire a bit. Probably instead of wildcards we should be thoughtful about the specific things we export.
But then:
import typelevel.toolkit.*
and you are off to the races!
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 the proposed typelevel.toolkit package and the specific exports suggested in the issue. The work is done when the project has an agreed, maintainable export set and the documented single-package import works without introducing problematic conflicts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100