PAGOPA-1622 inserting flag standin logic in api #322
Closed
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
|
…ag-stand-in-per-wsdl [skip ci]
…ag-stand-in-per-wsdl [skip ci]
FedericoRuzzier
deleted the
PAGOPA-1622-sviluppo-api-config-gestione-flag-stand-in-per-wsdl
branch
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.
List of Changes
Adding flag standin logic to channels and stations apis
Motivation and Context
Needed in order to properly modify the standin field on stations and channels. The field is necessary to BO.
How Has This Been Tested?
Manually and through junit tests
Screenshots (if appropriate):
Types of changes
Checklist: