[AAE-6093] - fixed rest option for cloud widget #7304
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
VitoAlbano
requested review from
DenysVuika,
eromano and
popovicsandras
as code owners
|
|
eromano
requested changes
Oct 19, 2021
...vices-cloud/src/lib/form/components/widgets/radio-buttons/radio-buttons-cloud.widget.spec.ts
Outdated
Show resolved
Hide resolved
...rocess-services-cloud/src/lib/form/components/widgets/dropdown/dropdown-cloud.widget.spec.ts
Show resolved
Hide resolved
VitoAlbano
added
depends on activitity
Waiting for another branch to be merged
and removed
depends on activitity
labels
VitoAlbano
force-pushed
the
dev-valbano-AAE-6093
branch
from
d5a0372
to
c085426
Compare
eromano
requested changes
Oct 29, 2021
…est url with the new feature
VitoAlbano
force-pushed
the
dev-valbano-AAE-6093
branch
from
faa4813
to
ad62bc4
Compare
eromano
approved these changes
Oct 29, 2021
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)
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: