Skip to content
This repository has been archived by the owner on Sep 27, 2021. It is now read-only.

Remove extra top-level libraries #58

Open
natebosch opened this issue Jun 7, 2021 · 1 comment
Open

Remove extra top-level libraries #58

natebosch opened this issue Jun 7, 2021 · 1 comment
Labels
next-breaking-release Issues that are worth doing but need to wait for a breaking version bump

Comments

@natebosch
Copy link

The modern pattern for most packages is to use a single top-level import library and put the implementation libraries in lib/src. We don't typically ship fine-grained libraries unless there is a specific use case like supporting platform specific imports.

@natebosch natebosch added the next-breaking-release Issues that are worth doing but need to wait for a breaking version bump label Jun 7, 2021
@lrhn
Copy link
Contributor

lrhn commented Jun 16, 2021

Would be reasonable if we ever make a 3.0 release. We likely won't.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
next-breaking-release Issues that are worth doing but need to wait for a breaking version bump
Development

No branches or pull requests

2 participants