-
Notifications
You must be signed in to change notification settings - Fork 112
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
Result is both a namespace and a type #93
Comments
Agreed and it's a problem. Obviously would be a breaking change. I think the type name should remain which means the namespace and possibly the package would need to change. Thoughts? Ardalis.Result (obsolete/redundant) other ideas? |
I like Giving a namespace to something as narrow as But if you want to a separate namespace for just Ardalis.ResultAbstraction |
Ardalis.Results came up in Discord and is one I'm leaning toward. Still considering if we should also do something to help differentiate from the new |
Here are some examples from two other popular result libraries. This uses the root namespace This uses Neither seem to be ideal for this situation so my vote would be to use the plural form |
The namespace of the derived classes of |
As of #89,
Result
is both a namespace and a type. This is bad practice. Conceptually, the type name is ideal, but the namespace already exists.Thoughts?
The text was updated successfully, but these errors were encountered: