What's the specific use case? What's the logic that determines availability (e.g., is this an auth/auth issue)?
An interceptor or action base class would be my first approach. On Wed, Mar 25, 2020 at 10:39 Matias Rodriguez <matias.rodrig...@gmail.com> wrote: > Hi! > > I'm looking for a clean way to disable/enable (at runtime) specific > namespace / specific action hierarchy. An option is to use an Interceptor, > but: is there another *standard *way to do this? With *disable* I mean, for > example, a HTTP 404 server response. > > Thanks! > -- em: davelnew...@gmail.com mo: 908-380-8699 tw: @dave_newton <https://twitter.com/dave_newton> li: dave-newton <https://www.linkedin.com/in/dave-newton/> gh: davelnewton <https://github.com/davelnewton> so: Dave Newton <http://stackoverflow.com/users/438992/dave-newton> bl[0]: Bucky Bits <http://buckybits.blogspot.com/> bl[1]: Maker's End Blog <https://blog.makersend.com> sk: davelnewton_skype
