Encode does not respect Style = LiteralStyle #1041
Comments
|
Turns out trailing spaces cause it: |
5 tasks
efd6
added a commit
to efd6/integrations
that referenced
this issue
Jan 30, 2025
We see situations where the CEL program is rendered in double quoted strings in the pre-config.yml in diagnostic bundles, making it difficult to read. The cause of this has now been identified as the presence of trailing whitespace on lines[1]. So remove those. [1]go-yaml/yaml#1041 (comment)
efd6
added a commit
to elastic/integrations
that referenced
this issue
Jan 30, 2025
We see situations where the CEL program is rendered in double quoted strings in the pre-config.yml in diagnostic bundles, making it difficult to read. The cause of this has now been identified as the presence of trailing whitespace on lines[1]. So remove those. [1]go-yaml/yaml#1041 (comment)
harnish-elastic
pushed a commit
to harnish-elastic/integrations
that referenced
this issue
Feb 4, 2025
We see situations where the CEL program is rendered in double quoted strings in the pre-config.yml in diagnostic bundles, making it difficult to read. The cause of this has now been identified as the presence of trailing whitespace on lines[1]. So remove those. [1]go-yaml/yaml#1041 (comment)
qcorporation
pushed a commit
to elastic/integrations
that referenced
this issue
Feb 4, 2025
We see situations where the CEL program is rendered in double quoted strings in the pre-config.yml in diagnostic bundles, making it difficult to read. The cause of this has now been identified as the presence of trailing whitespace on lines[1]. So remove those. [1]go-yaml/yaml#1041 (comment)
harnish-elastic
pushed a commit
to harnish-elastic/integrations
that referenced
this issue
Feb 5, 2025
We see situations where the CEL program is rendered in double quoted strings in the pre-config.yml in diagnostic bundles, making it difficult to read. The cause of this has now been identified as the presence of trailing whitespace on lines[1]. So remove those. [1]go-yaml/yaml#1041 (comment)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Running the following program shows the issue; https://go.dev/play/p/dbduWiFiGZO.
Despite setting Style to LiteralStyle for all nodes, the string is printed as a quoted string. The choice of behaviour can be altered by removing some text, though which parts cause the change in behaviour is unclear (for example, this https://go.dev/play/p/AwdkIx8FBSJ gives the desired behaviour with literal string being rendered).
The text was updated successfully, but these errors were encountered: