UI backend #141
Merged
UI backend #141
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fishkerez
force-pushed
the
ui-backend
branch
2 times, most recently
from
8d9397d
to
0c2a6b3
Compare
FrimIdan
reviewed
Mar 15, 2023
akpsgit
previously approved these changes
Mar 16, 2023
FrimIdan
previously approved these changes
Mar 16, 2023
FrimIdan
approved these changes
Mar 16, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
In order to simplify logic that consist of many API calls in the UI, we’ll create a new “micro-service“ that will have its own OAS. The UI backend instance will be instantiated temporarily from backend (similar to the orchestrator) and will be registered on a separate API endpoint in the echo middleware.
The OAS will contain a single path for each widget, which the UI backend will handle by making all the relevant API calls to the backend API (and NOT access the db handler). The UI backend will response for each API path with all the needed information to render the dashboard widget.
This commit is the infrastructure for the UI backend, on top of it we will build all the needed UI apis.
Type of Change
[ ] Bug Fix
[ *] New Feature
[ ] Breaking Change
[ ] Refactor
[ ] Documentation
[ ] Other (please describe)