I ran this to update all of my existing blueprints, and while most of them worked, several of them were broken due to two main issues:
- On multiline strings that start with >, the > character is replaced with
>
- On values that contain double quotes, they are all escaped with a backslash which sometimes changes their meaning or makes values that should be quoted act as if they aren't quoted.
Is there a reason it does this, or is this unintended behavior?
If this matters, I did call the script to update all blueprints from the automation provided in the docs, rather than by manually using the command line.
I ran this to update all of my existing blueprints, and while most of them worked, several of them were broken due to two main issues:
>Is there a reason it does this, or is this unintended behavior?
If this matters, I did call the script to update all blueprints from the automation provided in the docs, rather than by manually using the command line.