-
Notifications
You must be signed in to change notification settings - Fork 8
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
🐞 [Bug]: Normalize the virtual machine subdomain #2564
Comments
Can users choose a subdomain without a prefix, if the name is not reserved? If not feasible, we can start with the user's chosen name and add a suffix afterward. |
@sameh-farouk |
Work completed: Removed twinId & solution name and edited subdomain char limit to 5 + prefix (VM name). |
WIP: Reverted previous changes and currently working on combining both the prefix and the subdomain as a name and allow the user to edit both. However, a validation would be triggered to check if a name contract exists with the same name or not to avoid post-deployment errors. |
Work completed: Created a validation rule to check if a name contract with the same name exists on the chain or not. Edited the subdomain to include the prefix by default and changed the max limit to 15 instead of 35. Also, edited the subdomain tooltip and the name in the table accordingly. |
After creating a domain, the same name validation isn't working. Maybe you should randomize naming every time dialogue is reopened. |
Work Completed: Validate subdomain if tab is changed, change tab condition to v-if instead of v-show so the validation condition to work. |
Verified, Devnet 17d861b. |
Is there an existing issue for this?
which package/s did you face the problem with?
Dashboard
What happened?
The subdomain is too long
Steps To Reproduce
which network/s did you face the problem on?
Dev
version
2.3.4
Twin ID/s
143
Node ID/s
NA
Farm ID/s
NA
Contract ID/s
NA
Relevant screenshots/screen records
Relevant log output
NA
The text was updated successfully, but these errors were encountered: