Add "legacy compose" new route fetch #76
Merged
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
antoineludeau
force-pushed
the
antoineludeau/add-legacy-compose-new-route-fetch
branch
from
d3939ca
to
0606b06
Compare
antoineludeau
requested review from
nkokla,
mmortier,
vinsag,
IGNFBourcier and
FLoreauIGN
nkokla
approved these changes
Mar 10, 2024
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.
Context
In order to redirect to the legacy compose when a district does not use the BAN-IDs, we need to add a route call.
Enhancements
This PR adds a post call to a new Ban-plateforme route :