Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ACS-5949] library property update and cancel button do not reflect the change in UI #3461

Conversation

AleksanderSklorz
Copy link
Contributor

Please check if the PR fulfills these requirements

  • The commit message follows our guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (check one with "x")

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Documentation
  • Other... Please describe:

What is the current behaviour? (You can also link to an open issue here)
https://alfresco.atlassian.net/browse/ACS-5949

What is the new behaviour?
Update button is disabled when changes are saved and cancel restores proper values for fields.

Does this PR introduce a breaking change? (check one with "x")

  • Yes
  • No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...

Other information:

@AleksanderSklorz AleksanderSklorz force-pushed the ACS-5949-library-property-update-and-cancel-button-do-not-reflect-the-change-in-UI branch from 0f4e1fd to 856c958 Compare October 4, 2023 13:38
@DenysVuika DenysVuika merged commit 4059a3d into develop Oct 5, 2023
27 checks passed
@DenysVuika DenysVuika deleted the ACS-5949-library-property-update-and-cancel-button-do-not-reflect-the-change-in-UI branch October 5, 2023 07:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants