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
Currently, any route mounted within a Flama app is visible to the outside world without any restriction. However, it could be that users of the library want to expose certain routes only for authenticated users of theirs, with certain permissions. For this to happen, one of the requirements will be that the routes "know" which permissions are needed for them to be accessible.
Proposed solution
The interface of the solution could look something like:
However, this hack does not give the granularity of having different permissions etc. which is why we think implementing this as a fundamental feature of Flama is needed.
The text was updated successfully, but these errors were encountered:
Context
Currently, any route mounted within a
Flama
app is visible to the outside world without any restriction. However, it could be that users of the library want to expose certain routes only for authenticated users of theirs, with certain permissions. For this to happen, one of the requirements will be that the routes "know" which permissions are needed for them to be accessible.Proposed solution
The interface of the solution could look something like:
which, at some point will involve adding to the tags of the resource such permissions passed as arguments before, i.e.:
Indeed, a mokey-patching strategy would consist in doing the following:
However, this hack does not give the granularity of having different permissions etc. which is why we think implementing this as a fundamental feature of
Flama
is needed.The text was updated successfully, but these errors were encountered: