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
When clicking on a keyword to delete it, the project form is submitted. This happens because any button inside a <form> has type=submit by default. You need to set type=button to disable this behavior.
Clicking on a keyword to delete it is not an intuitive way to do it. Users expect to have a delete button, like these:
When there is no input in the keyword search box, the existing keywords are not discoverable. We might want to see the list of currently existing keywords, and use the search box to filter them (or create if required).
Minor issue. Whenever a keyword is added, there is a request to /api/tag/create, even if the keyword already exists. This request replies with the existing keyword. I would expect no request to be made as we already have everything we need on the front-end.
The text was updated successfully, but these errors were encountered:
When clicking on a keyword to delete it, the project form is submitted. This happens because any button inside a
<form>
hastype=submit
by default. You need to settype=button
to disable this behavior.Clicking on a keyword to delete it is not an intuitive way to do it. Users expect to have a delete button, like these:
When there is no input in the keyword search box, the existing keywords are not discoverable. We might want to see the list of currently existing keywords, and use the search box to filter them (or create if required).
Minor issue. Whenever a keyword is added, there is a request to
/api/tag/create
, even if the keyword already exists. This request replies with the existing keyword. I would expect no request to be made as we already have everything we need on the front-end.The text was updated successfully, but these errors were encountered: