-
Notifications
You must be signed in to change notification settings - Fork 0
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
Keep React Frontend app and BFF app communication in sync #34
Comments
The 4th of October Simen and Torgeir had a long meeting on the topic of API calls, and how to keep Swagger documentation, Issue-documentation (#8 ), and Wiki-documentation in sync. The meeting also resulted in a drastic simplification of the userInfo API call, and the deprecation of the fetchReporteeInfo API call (see issue #8 ). |
09.10.23 Update: Dotnet app being rebuilt for Cookie use, so React frontend app is now being accessed directly. See repo wiki for update and direct links. |
09.11.23 The pull-down API now works. Possibly the DTO should be modified to include an "empty" first object, |
The frontend repo README is lagging in its quality. The How-to-use information should be updated in light |
The cleanup after the new designs of 24.11.23 broke a lot of API, |
A common problem in software development is lack of clarity at the interface between systems.
In our case we have a BFF app running as a Backend-for-Frontend
to serve API calls from the React frontend app.
It is important that the interface between frontend and BFF is clear to all
interested parties. Also see issue #7 and issue #8.
Today, 29.09.23, the two apps are now running and communicating,
see README documentation in sub-repos and main repo.
We intend to keep the two apps in sync, to avoid future problems.
Tasks
The text was updated successfully, but these errors were encountered: