You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today, the GetFluentApiCalls and GetDataAnnotations extensions used by the templates automatically filter out configurations that will be handled by conventions. It would be nice if the user could still choose to include these in the generated code.
I imagine that we'd add a property like IsHandledByConventions to the returned objects. And just filter them back out in the templates.
Then if users want, for example, to always include validation attributes (#9580), the templates could include code like this.
Today, the
GetFluentApiCalls
andGetDataAnnotations
extensions used by the templates automatically filter out configurations that will be handled by conventions. It would be nice if the user could still choose to include these in the generated code.I imagine that we'd add a property like
IsHandledByConventions
to the returned objects. And just filter them back out in the templates.Then if users want, for example, to always include validation attributes (#9580), the templates could include code like this.
The text was updated successfully, but these errors were encountered: