Context Navigation

Changes between Initial Version and Version 1 of Ticket #31324, comment 12

initial	v1
1		If we're going to conjecture, I think in reality most users set a default, such as `dict`, so they don't have empty fields... — but I stand by point: if you're using JSONField you're best off setting `null` as the empty value, so all fields contain JSON.
	1	If we're going to conjecture, I think in reality most users set a default, such as `dict`, so they don't have empty fields... — but I stand by the point: if you're using JSONField you're best off setting `null` as the empty value, so all fields contain JSON.
2	2
3	3	For this ticket, the relevant point it that I don't think we should have the API favour SQL-like usage over JSON-like usage. And I really don't think `=None` should behave differently for the base field as against a nested key. JSONFields aren't quite the same as other fields OK—can we doc that better—but they should be internally consistent so if I'm using one, I can have reasonable expectations about how they'll behave.