U1db.Document silently ignores key assignment

[Sam Bull]

"document.contents[foo] = bar" has no effect.

This results in needing to write the above code as:
  var temp = document.contents
  temp[foo] = bar
  document.contents = temp

This is annoying and ugly code everytime I want to update a single value.

Proposed solution:
  Allow saving keys directly.

  If for some reason this is absolutely not possible, atleast throw an error or display a warning when an assignment is attempted, as it is clearly not the desired behaviour that the above line of code does absolutely nothing.

[Cris Dywan (kalikiana)]

This is QVariant, specifically how variants in QML behave, and not deliberate on U1Db's part.

The only way to address this would be to re-consider the API or try to replace QVariant.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.