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

Break project into sub-packages #95

Open
amichair opened this issue Mar 7, 2019 · 0 comments
Open

Break project into sub-packages #95

amichair opened this issue Mar 7, 2019 · 0 comments

Comments

@amichair
Copy link
Contributor

amichair commented Mar 7, 2019

This is a general design note, perhaps for a 2.0.0 release since it breaks backwards compatibility: I would suggest maybe to reorganize the org.passay package into separate sub-packages - one for rules, one for character data/sequences, one for message handling, one for core data objects (password data, references, etc.), one for utilities etc. or some other division that makes sense. The current mix of all classes in one package (except dictionary classes which do have their own subpackage) makes it a bit harder to work with and to clearly see the project design and structure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant