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

fix(header) ensure instance name is unique and ot matched against previous name #805

Merged
merged 2 commits into from
Jun 25, 2024

Conversation

edlerd
Copy link
Collaborator

@edlerd edlerd commented Jun 25, 2024

Done

  • ensure instance name is unique and not matched against previous name on renaming

QA

  1. Run the LXD-UI:
  2. Perform the following QA steps:
    • rename an instance
    • change name to the same name as the current name. Previously it would cause a validation error, now it should be fine.

@webteam-app
Copy link

@mas-who
Copy link
Contributor

mas-who commented Jun 25, 2024

code looks good and can confirm no validation error occurs once name is changed 🙂

I found a pre-existing behaviour that's a bit strange:

  1. click on the rename header
  2. change the instance name but don't save
  3. click cancel
  4. click on the rename header again and it shows the changed name in step 2.

Is this intended behaviour?

@edlerd
Copy link
Collaborator Author

edlerd commented Jun 25, 2024

  1. click on the rename header
  2. change the instance name but don't save
  3. click cancel
  4. click on the rename header again and it shows the changed name in step 2.

Is this intended behaviour?

This is not ideal. Added a change to reset the value in the form on cancel.

@edlerd edlerd requested a review from mas-who June 25, 2024 06:44
@mas-who
Copy link
Contributor

mas-who commented Jun 25, 2024

LGTM, thanks for the fix 👍

@edlerd edlerd merged commit 616fa5d into canonical:main Jun 25, 2024
12 checks passed
@edlerd edlerd deleted the fix-instance-rename branch June 25, 2024 08:35
github-actions bot pushed a commit that referenced this pull request Jun 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants