You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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).
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.
The text was updated successfully, but these errors were encountered: