adrianheine added a comment.

I think the current behavior is not too bad. The Wikibase JavaScript code found 
some value it cannot allow you to edit because the UI is not able to represent 
the current state. What's broken about this is that the UI is not able to 
handle non-standard calendar models, but that's more of a feature request than 
a bug. We might also think about how to make the JS code more fail-safe, so 
that at least the remainder of it is executed when it encounters such an error, 
but I find that to be a minor problem.

This is just the kind of issue you get when your data model and API support 
more than your UI does. In that case, crashing is a much better choice of 
action than for example silently dropping or overwriting the non-supported 
value.


TASK DETAIL
  https://phabricator.wikimedia.org/T89698

REPLY HANDLER ACTIONS
  Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign 
<username>.

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: thiemowmde, adrianheine
Cc: Lydia_Pintscher, hoo, aude, JanZerebecki, Addshore, adrianheine, 
thiemowmde, Snaterlicious, Balu, Aklapper, Wikidata-bugs, Jdouglas



_______________________________________________
Wikidata-bugs mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

Reply via email to