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
In the Desktop app, when creating a new service (i.e. the "Share a service" window), the Name value contains a prefix that is constant, so it shouldn't be visible to the user.
Desired
The Name placeholder should just contain the service name without the /service/ prefix.
The app backend doesn't need to be updated, as it already sanitizes the service name value and accepts both /service/name and name formats.
We love helping new contributors! If you have questions or need help as you work on your first Ockam contribution, please leave a comment on this discussion. If you're looking for other issues to contribute to, checkout this discussion and labels -
good first issue
or
help wanted
The text was updated successfully, but these errors were encountered:
adrianbenavides
changed the title
The “Name” should not have “/service/” prefix, just “outlet”
The "Name" should not have "/service/" prefix, just "outlet"
Aug 21, 2023
adrianbenavides
changed the title
The "Name" should not have "/service/" prefix, just "outlet"
In the Share a service window, the name attribute should not have the "/service/" prefix
Aug 21, 2023
adrianbenavides
changed the title
In the Share a service window, the name attribute should not have the "/service/" prefix
In the Share a service window, the Name attribute should not have the "/service/" prefix
Aug 21, 2023
adrianbenavides
changed the title
In the Share a service window, the Name attribute should not have the "/service/" prefix
In the Share a service window, the Name attribute should not have the /service/ prefix
Aug 21, 2023
Current
In the Desktop app, when creating a new service (i.e. the "Share a service" window), the
Name
value contains a prefix that is constant, so it shouldn't be visible to the user.Desired
The
Name
placeholder should just contain the service name without the/service/
prefix.The app backend doesn't need to be updated, as it already sanitizes the service name value and accepts both
/service/name
andname
formats.We love helping new contributors!
If you have questions or need help as you work on your first Ockam contribution, please leave a comment on this discussion.
If you're looking for other issues to contribute to, checkout this discussion and labels - good first issue or help wanted
The text was updated successfully, but these errors were encountered: