Gracefully handle unsupported qualifiers

Authored by matthiasmullie on Apr 9 2019, 1:03 PM.

Unpublished Commit · Learn More

Not On Permanent Ref: This commit is not an ancestor of any permanent ref.


Gracefully handle unsupported qualifiers

This should change nothing for what's currently already
possible in the interface.
However, it is possible that users submit other qualifiers
via custom API calls, potentially even with datatypes not
yet supported.

This patch will:

  • add other qualifiers (not defined in $wgDepictsQualifierProperties) to the properties dropdown when editing those properties, so they reflect reality
  • display a disabled input field with a "not supported" value for datatypes we don't yet support - thus allowing users to change or delete them (instead of flat out failing to deal with statements that have such content)

Bug: T220616
Bug: T220617
Change-Id: I9eb9770a73d025c668639844ad9d691849d0297a