Use full name for generic types #673
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
DavidBoone
force-pushed
the
nonDefaultNamespaceGenerics
branch
from
1e2d81d to
3ed76cd
Compare
DavidBoone
force-pushed
the
nonDefaultNamespaceGenerics
branch
from
3ed76cd to
1e5a10b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use the full name for generic types not in any of the
_defaultNamespacesnamespaces.Instead of
public NpgsqlRange<int> ActiveWeeks { get; set; }Generates
public NpgsqlTypes.NpgsqlRange<int> ActiveWeeks { get; set; }BTW, thanks for the recent v7 release, huge improvements!