-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow multi-line string in var.json
#94
Comments
A bit off-topic, but it would be nice if the add-on configuration UI could support multiline strings too. |
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. |
I'll try to take a look at this. |
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. |
Proposed a fix at #104 |
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. |
It's not fixed yet, #104 just requires a review. |
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. |
Still valid. |
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. |
Problem/Motivation
This was the goal, so that users could set something like:
Expected behavior
To produce a valid JSON with properly escaped line breaks and so.
Actual behavior
Steps to reproduce
I think the command above should be enough to replicate the issue.
Proposed changes
None yet.
The text was updated successfully, but these errors were encountered: