Similar to the way removing the last representation of a form is not allowed.

In T198035#4314903, @RazShuty wrote:

Similar to the way removing the last representation of a form is not allowed.

Example of that on forms in the current state would be:

Example response from the API:

{"errors":[{"code":"unprocessable-request","data":{"messages":[{"name":"wikibaselexeme-api-error-form-must-have-at-least-one-representation","parameters":[],"html":{"*":"Form must have at least one representation"}}]},"module":"main","*":"Form must have at least one representation"}],"servedby":"deployment-mediawiki-09","*":"See https://wikidata.beta.wmflabs.org/w/api.php for API usage. Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce> for notice of API deprecations and breaking changes."}

Should the UI also prevent this (disable the “remove” of the last gloss, or disable the “save” button if all glosses are gone), or should there only be a backend error? (Note that for forms, the UI currently doesn’t delete the last representation, according to @Addshore.)

@Lydia_Pintscher what about graying out the “remove” button of the last gloss instead of graying out the “save” button when the glosses are empty? I’ve implemented that for form representations as an experiment, and it feels more natural to me this way.

Edit: now a separate task, see T199703

Change 446285 had a related patch set uploaded (by Lucas Werkmeister (WMDE); owner: Addshore):
[mediawiki/extensions/WikibaseLexeme@master] Add ChangeOps for editing senses

https://gerrit.wikimedia.org/r/446285

I'm ok either way. Could you check with UX please?

@Lucas_Werkmeister_WMDE’s suggestion seems sensible, particularly since he tried already. I see the advantage that we block on the concerning thingy, not on the save button in general.

I want to point out that we might need to review this and other behavior from the point of UX so there might be changes to it (e.g. in this case we might need an error message or so). Or general: UX is behavior as well as looks and not all problems can be solved with another visual design (few can, actually).

This is not to discount efforts to make the best out of what can be done now (as trying it out was, I think, and helped greatly!). We just need to keep in mind that it might need some changes in the future beyond colors and position of elements – this is, behavior of features and UI (and I guess using vue.js it will be easier to do such changes!) (@WMDE-leszek @Lydia_Pintscher )

Change 450599 had a related patch set uploaded (by Lucas Werkmeister (WMDE); owner: Lucas Werkmeister (WMDE)):
[mediawiki/extensions/WikibaseLexeme@master] Prevent empty sense glosses in front-end

https://gerrit.wikimedia.org/r/450599

Change 450599 merged by jenkins-bot:
[mediawiki/extensions/WikibaseLexeme@master] Prevent empty sense glosses in front-end

https://gerrit.wikimedia.org/r/450599