Make Location, Message, MessageContent and Tag comparisons case-sensitive

It makes more sense for their data.
This commit is contained in:
Oliver Hamlet
2018-10-20 12:48:21 +01:00
parent fa37dc6754
commit b142dd1a8f
14 changed files with 68 additions and 55 deletions
+1 -1
View File
@@ -22,7 +22,7 @@ The scalar form is simply the value of the map form's ``link`` key. Using the sc
Equality
--------
Two location data structures are equal if the lowercased values of their ``link`` keys are identical.
Two location data structures are equal if the values of their ``link`` keys are identical.
Examples
--------
+2 -6
View File
@@ -57,12 +57,8 @@ If a message's ``content`` value is a string, the message will use the string as
Equality
--------
The equality of two message data structures is determined by comparing the values of their ``content`` keys. As the values of the keys can be different types, a comparison value is selected for each message using the following logic:
* If a value's type is a localised content list, then the English content string in that list is selected as the comparison value.
* If a value's type is a string, then that string is selected as the comparison value.
The two message data structures are then equal if their lowercased comparison values are identical.
The equality of two message data structures is determined by comparing the values of their ``content`` keys. If a content key is a string, it is treated as a localised content list
containing a single English-language string. The two message data structures are then equal if their localised content lists are identical.
Examples
--------
+1 -1
View File
@@ -22,7 +22,7 @@ The scalar form is simply the value of the map form's ``name`` key. Using the sc
Equality
--------
Two tag data structures are equal if the lowercased values of their ``name`` keys are identical.
Two tag data structures are equal if the values of their ``name`` keys are identical.
Examples
--------