[AAE-6660] FE - [ADF] Linked dropdown still contains old options when the rest api does not return results #7454
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
|
|
sivakumar414ram
force-pushed
the
dev-siva-AAE-6660-drop-down-contains-old-options-url
branch
from
a404e27
to
ff15236
Compare
sivakumar414ram
requested review from
DenysVuika,
eromano and
popovicsandras
as code owners
… the rest api does not return results
sivakumar414ram
force-pushed
the
dev-siva-AAE-6660-drop-down-contains-old-options-url
branch
from
ff15236
to
bf47609
Compare
arditdomi
approved these changes
Jan 21, 2022
sivakumar414ram
deleted the
dev-siva-AAE-6660-drop-down-contains-old-options-url
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.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x")
What is the current behaviour? (You can also link to an open issue here)
https://alfresco.atlassian.net/browse/AAE-6660
What is the new behaviour?
Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information: