You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Noticed that Kaoto doesn't always quote values when it might need to. For instance, for the REST Component, there's a bindingMode parameter. It's an enum and one of the possible values is "off". So Kaoto generates bindingMode: off instead of bindingMode: "off". Which causes the YAML to interpret the value as "false" instead of the literal "off".
Steps to Reproduce the Bug or Issue
Create a new route
Add a rest producer
Set the bindingMode parameter to "off"
Inspect the YAML
Screenshots or Videos
No response
Platform
OS: all
Browser: all
Version: 0.14.0
The text was updated successfully, but these errors were encountered:
Currently, Kaoto serialize to YAML using YAML 1.2.
This creates an edge for the Rest component since one of its parameters
(`bindingMode`) accepts an `off` value which ultimately gets serialized as it is,
causing to be interpreted as `false`.
This commit change the YAML serializing schema to 1.1 so `off` gets serialized as `"off"`
avoiding this issue.
fix: KaotoIO#971
Currently, Kaoto serialize to YAML using YAML 1.2.
This creates an edge for the Rest component since one of its parameters
(`bindingMode`) accepts an `off` value which ultimately gets serialized as it is,
causing to be interpreted as `false`.
This commit change the YAML serializing schema to 1.1 so `off` gets serialized as `"off"`
avoiding this issue.
fix: #971
Describe the Bug
Noticed that Kaoto doesn't always quote values when it might need to. For instance, for the REST Component, there's a
bindingMode
parameter. It's an enum and one of the possible values is "off". So Kaoto generatesbindingMode: off
instead ofbindingMode: "off"
. Which causes the YAML to interpret the value as "false" instead of the literal "off".Steps to Reproduce the Bug or Issue
Screenshots or Videos
No response
Platform
The text was updated successfully, but these errors were encountered: