The current namespace and package is not prefixed with anything and could potentially clash with other packages in the future. At the 3.x release it might be a suitable time to consider prefixing the namespace to reduce this risk.
Considerations:
If renaming the package then this needs consideration in NuGet as users will not be notified of a new version if the package is renamed.
The current namespace and package is not prefixed with anything and could potentially clash with other packages in the future. At the 3.x release it might be a suitable time to consider prefixing the namespace to reduce this risk.
Considerations: If renaming the package then this needs consideration in NuGet as users will not be notified of a new version if the package is renamed.