Feature #27: Hook client to server endpoints#40
Merged
Conversation
raphael-frank
force-pushed
the
feature/27-hook-client-to-server-end-points
branch
from
654b45d to
6f3b210
Compare
Collaborator
|
I rebased onto #42 so the routing will be correct after merging. Rest lgtm! |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Replaces the placeholder mock /hello responses in the web-client with real HTTP calls to the Spring services. To avoid cross-origin (CORS) requests, all API traffic is routed through a single origin: Traefik routes /api//* on the web-client entrypoint to the matching backend, stripping the prefix so each service sees its native paths. Also wires up the organization and feedback services so all six backends are reachable from the client.
Closes #27