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
{{ message }}
This repository was archived by the owner on Dec 20, 2018. It is now read-only.
I guess it has been in Microsoft.AspNetCore.Builder all this time, this used to be the pattern so intellesense would work before we switched consistently to lambdas everywhere... Seems like we should welcome the options class home. This realistically shouldn't break many apps, as its rare for the options type to be used by itself without any other identity classes... Maybe something we can do post preview 2... @ajcvickers
The text was updated successfully, but these errors were encountered:
@ajcvickers ok for me to move the options type to the proper namespace now? We already moved it to a different assembly in (Extensions), might as well move it to the proper home namespace
I guess it has been in Microsoft.AspNetCore.Builder all this time, this used to be the pattern so intellesense would work before we switched consistently to lambdas everywhere... Seems like we should welcome the options class home. This realistically shouldn't break many apps, as its rare for the options type to be used by itself without any other identity classes... Maybe something we can do post preview 2... @ajcvickers
The text was updated successfully, but these errors were encountered: