Actions
Bug #22940
closed
Empty key in json node property is accepted
Status:
Rejected
Priority:
N/A
Assignee:
Category:
Web - Nodes & inventories
Target version:
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
I dislike using that feature
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Priority:
65
Name check:
To do
Fix check:
To do
Regression:
No
Description
In 7.2 we can do : 
It's not accepted in 7.3
Files
Updated by Elaad FURREEDAN 11 months ago
- UX impact set to I dislike using that feature
- User visibility set to Infrequent - complex configurations | third party integrations
- Priority changed from 0 to 65
Updated by François ARMAND 11 months ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND 11 months ago
I don't understand what it breaks?
The bug is likely in 7.3 where it is not accepted anymore. Empty key are part of json spec (see for ex https://stackoverflow.com/a/58917082). This is not the property name (which must not be empty)
Then, I don't know why someone would like to do that, but I don't see how is it for us to judge it.
Updated by François ARMAND 11 months ago
- Status changed from In progress to Rejected
So, this is working as the JSON ECMA norm dictates. The fact that some OS native tooling (Windows, I'm looking at you) does not follow the spec and reject it is none of our business.
We need to ensure that each agent can correctly accomodate malformed/unparsable (for the os) JSON, though - which will be done in other tickets if any such problem is found.
Actions