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

Reconsider namespace organization as these projects mature. #3

Open
ppervink opened this issue Feb 3, 2019 · 1 comment
Open

Reconsider namespace organization as these projects mature. #3

ppervink opened this issue Feb 3, 2019 · 1 comment
Assignees
Labels
invalid This doesn't seem right

Comments

@ppervink
Copy link
Owner

ppervink commented Feb 3, 2019

Currently all classes are thrown within the root namespace of each project. As the other proposed features get implemented, I don't think this will continue to make sense.

This issue is intended as a reminder both to myself and to anyone that pulls this thing into their own projects that the namespaces (and possibly project organization) will most likely change in future iterations.

@ppervink ppervink added the invalid This doesn't seem right label Feb 3, 2019
@ppervink ppervink self-assigned this Feb 3, 2019
@ppervink
Copy link
Owner Author

ppervink commented Feb 3, 2019

Namespace organization will be an ongoing issue in any project before it reaches 1.0.0, but in general in the first few commits this will be in a higher level of flux than it will later on and at that time I'll keep most namespace changes after that point to a minimum (as you'd typically see in a more mature pre-release).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid This doesn't seem right
Projects
None yet
Development

No branches or pull requests

1 participant