Actions
Bug #22996
open
Property Json validation used to refuse unescaped '\' char, but it does not anymore
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No
Description
On windows we often use '\' to define paths, and by mistake I was able to define a Json property with a value like:
{ "foo": "C:\bar" }
And at execution time, the Path could not be resolved as the '\' was interpreted as a '\b' char.
I tested on a 7.2.2 Rudder and the same property definition was refused by the Json validation in the property webpage.
Looks like a regression, I am not sure of the impact here.
Updated by 
Updated by
Actions