-
Notifications
You must be signed in to change notification settings - Fork 256
Refactor to use annotation access pattern #716
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
Refactor to use annotation access pattern #716
Conversation
e78127d to
a9533ca
Compare
roji
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The overall direction is good and makes the good more clean/idiomatic. But please see notes about where the annotations belong.
b17fbfd to
e290f96
Compare
e290f96 to
cbfe6e9
Compare
|
@roji I took another pass at this with better naming and more specific extension methods (i.e. not on I think it's a step in the right direction, but may still need some refinement. |
roji
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks close to ready, see my comment about the interfaces.
For the record I don't think there's huge value in this - it does make for a slightly nicer interface to the annotation data, but lots of code is added to support this...
src/EFCore.PG/Metadata/INpgsqlAlterDatabaseOperationAnnotations.cs
Outdated
Show resolved
Hide resolved
e21fe78 to
1101084
Compare
I realized while working on #685 that
PostgresExtension,PostgresEnum, andPostgresRangebroke with (what seems like) the standard annotation access patterns used throughout EF Core.