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

Move exceptions into a sub-namespace #18

Open
airbreather opened this issue Jul 22, 2019 · 0 comments
Open

Move exceptions into a sub-namespace #18

airbreather opened this issue Jul 22, 2019 · 0 comments
Labels
binary breaking change enhancement New feature or request source breaking change usability Make the library easier to use
Milestone

Comments

@airbreather
Copy link
Owner

Something I neglected in 1.1.0 is to ensure that users have a decent experience when trying to discover Cursively's API through IntelliSense or the online API browser.

At the moment, all the new exception types added for the header-aware visitor simply live in the top-level "Cursively" namespace, which makes it harder to find the small handful of types that are meant to serve as starting points for the API.

Moving these to a Cursively.Exceptions namespace should help with this.

This would be a source and binary breaking change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
binary breaking change enhancement New feature or request source breaking change usability Make the library easier to use
Projects
None yet
Development

No branches or pull requests

1 participant