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
When refactoring to v4.0.0 I left FunctionAuthorizeAttribute in Isolated mode in place just to make migration easier for current In-Process consumers.
There has been confusion on when to use the attribute. It was only intended for migration, but the recommended type should be AuthorizeAttribute from ASP.NET Core Authorization framework.
In coming version I'm planning on marking the attribute as Obsolete and completely remove in later versions.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
When refactoring to v4.0.0 I left
FunctionAuthorizeAttributein Isolated mode in place just to make migration easier for current In-Process consumers.There has been confusion on when to use the attribute. It was only intended for migration, but the recommended type should be
AuthorizeAttributefrom ASP.NET Core Authorization framework.In coming version I'm planning on marking the attribute as
Obsoleteand completely remove in later versions.Beta Was this translation helpful? Give feedback.
All reactions