Evolving authentication on React components

This content originally appeared on Posts on LINQ to Fail and was authored by Posts on LINQ to Fail

In my last post I talked about how you can do Authentication on React components using mixins. Using a mixin to add role-based security to any component we create is really handy but it does have one real problem, you have to inherit that mixin on every component you want to have it on. It works well when you want to do something like hide links or buttons, but it starts to fall down when you want to hide sections of components, maybe a row in a table is only there for certain roles, or a section of a menu isn’t visible for everyone.

This content originally appeared on Posts on LINQ to Fail and was authored by Posts on LINQ to Fail