Description
Parse leftJson and rightJson as JSON numbers or strings.
Graph identifiers and endpoints describe different kinds of equality. Two edges can connect the same vertices while remaining distinct records, and serialized numeric or string identifiers can lose distinctions during parsing or normalization.
Parse leftJson and rightJson as JSON numbers or strings.
When to use this tool
Use Graph Node ID Type Collision Flag when you need a literal identifier or endpoint comparison with explicit coercion rules.
How to use the tool and how it works
- Enter leftJson, rightJson. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read sameSerializedText, typedEqual. Inspect sameSerializedText, typedEqual before interpreting the associated values.
Parse leftJson and rightJson as JSON numbers or strings. Compare their JavaScript String conversions for sameSerializedText and their parsed typed values for typedEqual.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| leftJson | Left Json | Required. Text; maximum UTF-16 length 8192. |
| rightJson | Right Json | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| sameSerializedText | Whether String(left) equals String(right), rather than equality of JSON serialization. | Required. Boolean. |
| typedEqual | Whether parsed values have equal primitive type and value. | Required. Boolean. |
{
"input": {
"leftJson": "1",
"rightJson": "\"1\""
},
"output": {
"sameSerializedText": true,
"typedEqual": false
}
}Limitations and assumptions
- The first flag is coerced display-text equality rather than equality of JSON spellings; JSON numeric conversion can lose decimal precision, and no graph ID is looked up or normalized.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Alternative or Complementary methods
Retain original identifiers and use a declared canonical representation for storage. Resolve actual edge identity through the graph's data model rather than endpoint coincidence alone.
References
Similar or alternative tools
- Graph Label Canonical Number String Guard
Require nonempty label, convert it to Number, and mark canonical only when it is a safe integer whose String conversion exactly matches the original label.
- Edge List Single Edge Canonical Order
Compare source and target using JavaScript string ordering, swap them when source is greater, and return reversed.