You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The NoPorts Dashboard allows importing a profile that includes a space at the end of the device atSign or the end of the device name.
Steps to reproduce
First I imported the yaml profile called "device-atSign-plus-space-profile"
The file was accepted even though the data in the file is invalid.
Then I tried importing the profile called "device-name-plus-space-profile". The file was accepted.
Expected behavior
In both cases I expected the NoPorts Dashboard to produce an error indicating the profile is invalid and why. Also, I had to hand edit the "device-name-plus-space-profile" to add the space at the end of the device name because the NoPorts Dashboard UI wouldn't allow me to add a device name that included a space. I included the two profiles but had to add the .txt extension.
Describe the bug
The NoPorts Dashboard allows importing a profile that includes a space at the end of the device atSign or the end of the device name.
Steps to reproduce
Expected behavior
In both cases I expected the NoPorts Dashboard to produce an error indicating the profile is invalid and why. Also, I had to hand edit the "device-name-plus-space-profile" to add the space at the end of the device name because the NoPorts Dashboard UI wouldn't allow me to add a device name that included a space. I included the two profiles but had to add the .txt extension.
device-atSign-plus-space-profile.yaml.txt
device-name-plus-space-profile.yaml.txt
Screenshots
Screen.Recording.2024-11-29.at.2.45.50.PM.mov
Smartphones
Were you using an atApplication when the bug was found?
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: