Simplify UseJwtAccessWithScopes
jskeet opened this issue · 0 comments
jskeet commented
We shouldn't bother generating complicated code in builders for UseJwtAccessWithScopes - we never "override" it anyway, as all APIs support it.
We can leave it as a protected property which defaults to being true (and stop generating the explicit parameterless constructors), and potentially make it public in the future. (We could just remove it entirely, but it feels useful to be able to potentially intervene.)
Filing this as a feature request in terms of simplifying the client code.