Skip to content

Conversation

@Leonabcd123
Copy link
Contributor

@Leonabcd123 Leonabcd123 commented Oct 31, 2025

Description

Updated input element to use the valid saved name instead of the current, potentially invalid one.

Closes #7064

@monkeytypegeorge monkeytypegeorge added the frontend User interface or web stuff label Oct 31, 2025
@Miodec
Copy link
Member

Miodec commented Oct 31, 2025

Thank you, however this is a bit of a band-aid fix. Sorry, but Ill commit a proper fix.

@Leonabcd123
Copy link
Contributor Author

Leonabcd123 commented Oct 31, 2025

Maybe if we can get it so when a user closes the edit preset name popup, it automatically updates it to the last saved name (that we know is valid), instead of the one currently in the input element?

@Miodec Miodec closed this in e930d0c Oct 31, 2025
@Leonabcd123 Leonabcd123 deleted the fix-invalid-preset-name branch October 31, 2025 17:19
@Miodec
Copy link
Member

Miodec commented Oct 31, 2025

Maybe if we can get it so when a user closes the edit preset name popup, it automatically updates it to the last saved name (that we know is valid), instead of the one currently in the input element?

I just opted for not checking the input if its not needed (when deleting). Seems to me like the solution that makes most sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

frontend User interface or web stuff

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Invalid preset name error when trying to delete a preset with an unsaved invalid name

3 participants