"convert to JS first, then encode" button in playground

[rohanmahy]

Option in the cbor2 playground

The sortKeys pulldown in the cbor2 playground has three options: null, coreDeterministic, lengthFirstDeterministic.

Current behavior

Regardless of the setting, the following map is encoded in the input order of its keys

{
   [1, 2, 3]: true,
   257: true,
   "a": true
}

Expected behavior

sortKeys = null: input order (as expected)

sortKeys = coreDeterministic: expected to sort the map keys in lexicographic order according to the rules of Section 4.2.1 of RFC 8949.

The output would be the same as:

   257: true,
   "a": true,
   [1, 2, 3]: true

Quoting that section:

The keys in every map MUST be sorted in the bytewise lexicographic order of their deterministic encodings. For example, the following keys are sorted correctly:

1. 10, encoded as 0x0a.
2. 100, encoded as 0x1864.
3. -1, encoded as 0x20.
4. "z", encoded as 0x617a.
5. "aa", encoded as 0x626161.
6. [100], encoded as 0x811864.
7. [-1], encoded as 0x8120.
8. false, encoded as 0xf4.

sortKeys = lengthFirstDeterministic: expected to sort the map keys in length-first, then lexicographic order of the value omitting the first 3-bit of the major as poorly described in the third bullet item of Section 3.9 of RFC7049.

The output would be the same as:

   "a": true,
   257: true,
   [1, 2, 3]: true

[hildjj]

What happens when you set the input type to js, and use the following input:

new Map([
   [[1, 2, 3], true],
   [257, true],
   ["a", true],
])

When I do that, the sorting options work as you expect.

[hildjj]

I now understand that you are inputting EDN. EDN gets converted to bytes then decoded into whatever format you want, so the encodeOptions don't really apply.

Leaving this open in case anyone wants a checkbox for "convert to JS first, then encode" for all of the input formats except for JS. You can achieve the same results by hitting the "Copy to input" at strategic points, so I'm not going to prioritize this unless someone's going to use it.