Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Interfaces hot load #276

Open
georgolden opened this issue Dec 11, 2021 · 1 comment
Open

Interfaces hot load #276

georgolden opened this issue Dec 11, 2021 · 1 comment
Assignees

Comments

@georgolden
Copy link
Member

#267

Is your feature request related to a problem? Please describe.

  1. 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.
  2. 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
({
 access: [ 'public', 'admin', 'group1', 'group2', etc.... ],
})

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.

@georgolden
Copy link
Member Author

@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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants