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
Is your feature request related to a problem? Please describe.
If we create new interface in application/api. We need to provide knowledge, to a client, that there is a new interface available. This can be done only manually inside the client application.
In most cases we have modern client application has a lot of states, we can make API stateful as well. We can have access rules for different interfaces and load only API, that client has access to. Public API, admin API, customer API etc...
Describe the solution you'd like
Get new interfaces names after Authentication/Authorization or even user access changing (user got banned for example) and update state of API in a client. Or after server updated API.
Create a way for a server to be able to send a specific event to a client, and client library must change API state as well.
Maybe provide a way to connect data access with a specific interface. We have access field optional in every interface method in a backend.
I suggest having some declarative schema with possible access field values, that will be connected to our access system. Example
Describe alternatives you've considered
More sophisticated connection between access system and interfaces.
Any suggestions, how to do it better will be super nice.
Additional context
If someone has any ideas connected to this feature request. Please share your ideas here. Every suggestion or improvement will be very welcome.
The text was updated successfully, but these errors were encountered:
@tshemsedinov please review access syntax. Do we have any blocks in impress development, that I should first wait for before start working on this feature?
#267
Is your feature request related to a problem? Please describe.
application/api
. We need to provide knowledge, to a client, that there is a new interface available. This can be done only manually inside the client application.Describe the solution you'd like
access
field optional in every interface method in a backend.access
field values, that will be connected to our access system. ExampleDescribe alternatives you've considered
More sophisticated connection between access system and interfaces.
Any suggestions, how to do it better will be super nice.
Additional context
If someone has any ideas connected to this feature request. Please share your ideas here. Every suggestion or improvement will be very welcome.
The text was updated successfully, but these errors were encountered: