fix: dash slug names

[fernandom06]

What this PR does / why we need it:

• Check slug in front to show error if is neccessary
• Default slug in backend if generated slug is empty

Before

After

Which issue(s) this PR fixes:

Fixes #5532

Special notes for your reviewer:

I have created a function to generate the slug in the frontend to be able to check it before sending it to the backend, I don't know if I should use some library like in the backend

Testing

Tested locally, w/Chrome dev tools for mobile UX.

[michael-genson]

Since we already do basically this on the backend, I think it would be better to keep the logic there and throw an error that we catch on the frontend. That way we don't duplicate the slug logic in both the frontend and backend.

We could even do a custom error message like "unable to generate slug" which the frontend could read. We already have some error messages that we directly show the user using i18n on the backend (though not many).

e.g. from LDAP:

if self.user.password == "LDAP" or self.user.auth_method == AuthMethod.LDAP:
    raise HTTPException(
        status.HTTP_400_BAD_REQUEST, ErrorResponse.respond(self.t("user.ldap-update-password-unavailable"))
    )

This will automatically flash an error to the user on the frontend (we have a custom plugin for this).

[fernandom06]

Since we already do basically this on the backend, I think it would be better to keep the logic there and throw an error that we catch on the frontend. That way we don't duplicate the slug logic in both the frontend and backend.

We could even do a custom error message like "unable to generate slug" which the frontend could read. We already have some error messages that we directly show the user using i18n on the backend (though not many).

e.g. from LDAP:

if self.user.password == "LDAP" or self.user.auth_method == AuthMethod.LDAP:
    raise HTTPException(
        status.HTTP_400_BAD_REQUEST, ErrorResponse.respond(self.t("user.ldap-update-password-unavailable"))
    )

This will automatically flash an error to the user on the frontend (we have a custom plugin for this).

Now when slug is invalid raise a SlugError, that I create in core.exceptions and raise a HTTPException in RecipeController class in recipe_crud_routes.py file