From 6977c4fd5c0a7c5a31a86067b9f92ea6ed670186 Mon Sep 17 00:00:00 2001 From: "Alex A. Naanou" Date: Sat, 17 Jan 2026 14:06:21 +0300 Subject: [PATCH] notes... Signed-off-by: Alex A. Naanou --- README.md | 3 +-- serialize.js | 10 ++++++++++ 2 files changed, 11 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 4f86745..56f8751 100644 --- a/README.md +++ b/README.md @@ -188,9 +188,8 @@ Extensions to JSON: ### Structural paths -### Recursion +### Recursion and internal linking -If an object is encountered ### null types diff --git a/serialize.js b/serialize.js index 5befb8a..e44e8af 100644 --- a/serialize.js +++ b/serialize.js @@ -8,6 +8,16 @@ * - get/set object by path * Object.get(..) / Object.set(..) * +* XXX try removing paths from refs and use the same indexes, the same +* system as with functions... +* + this will make the refs shorter +* - the deserialization would require the same "seen" logic as +* serialization -- reuse a function +* - the "seen" logic can depend on settings, i.e. would either +* require a sable algorithm that would be settings-agnostic +* a-la paths (preferred), or a way to transfer serialization +* settings... +* * XXX the current path implementation is fully complient to the task at * hand but it will not suite the diff task as there is no way to know * the meaning of the path element without seeing the object (map/set