Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re-structure modules for more reasonable layers' and components' separation #977

Open
wprzytula opened this issue Apr 9, 2024 · 0 comments
Assignees
Labels
API-breaking This might introduce incompatible API changes API-stability Part of the effort to stabilize the API

Comments

@wprzytula
Copy link
Collaborator

As we're heading towards 1.0, we should clean the module structure up as well.

There is especially one offender: the transport module, which contains essentially everything; the very name transport says nothing about its content.

In the following Doc, I propose a new structure of modules, along with rationale for that and a detailed structure of exports.
https://docs.google.com/document/d/1OalpdKhwJK0CrPjWg2-CTzi7vYtIO3AZG-IbeyYOC4g/edit?usp=sharing

The work described should be done together with considering the prelude module intended contents (#637).

@wprzytula wprzytula added API-breaking This might introduce incompatible API changes API-stability Part of the effort to stabilize the API labels Apr 9, 2024
@wprzytula wprzytula self-assigned this Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API-breaking This might introduce incompatible API changes API-stability Part of the effort to stabilize the API
Projects
None yet
Development

No branches or pull requests

1 participant