[GH-ISSUE #172] Empty field name behavior #85

New issue

Closed

opened 2026-05-23 08:29:50 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-23 08:29:50 -06:00

Owner

Originally created by @donl on GitHub (Oct 30, 2022).
Original GitHub issue: https://github.com/appy-one/acebase/issues/172

Originally assigned to: @appy-one on GitHub.

When seting or pushing a key-value pair, with an empty string "" for the key , an empty child node is created with the same key as its parent.

I doubt this is the desired behavior, but I leave that up to you.

Also, I see some quirks with creating invalid keys (eg: containing \) on a acebase-client, being cached locally and then finally failing on the server with some read locks. Let me know if I should create another ticket for this.

Originally created by @donl on GitHub (Oct 30, 2022). Original GitHub issue: https://github.com/appy-one/acebase/issues/172 Originally assigned to: @appy-one on GitHub. When `set`ing or `push`ing a key-value pair, with an empty string `""` for the `key` , an empty child node is created with the same `key` as its parent. I doubt this is the desired behavior, but I leave that up to you. Also, I see some quirks with creating invalid keys (eg: containing `\`) on a `acebase-client`, being cached locally and then finally failing on the `server` with some read locks. Let me know if I should create another ticket for this.

gitea-mirror

2026-05-23 08:29:50 -06:00

closed this issue
added the
bug
label

gitea-mirror commented

2026-05-23 08:29:54 -06:00

Author

Owner

@appy-one commented on GitHub (Oct 31, 2022):

Ok, sounds like I need to be a little less permissive on what can be used as key names

@appy-one commented on GitHub (Oct 31, 2022): Ok, sounds like I need to be a little less permissive on what can be used as key names