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
Very interesting issue, I didn't think about it with my original use-case of VAR=$(stoml file entry), which would have made it a single line, no matter what. (Hence the S in the name: simple.)
As mentioned above the original use-case was for Linux shell scripts to easily/concisely manage configuration options. In most cases, a space-separated list is more useful, because it can be further processed in, for example, loops.
In your case, adhering to the TOML specification is more important. Although this was never really the purpose, it's still an edge case that's worth fixing. In the latest v0.6.2 release, I've introduced a -m parameter. If you add this parameter, the input entry will be read as-is as a string and printed out as-is. This will work for this multi-line case. (This is contrary to the default case of reading everything as a list of strings and then concatenating it with spaces.)
I hope this is a good workaround for your case. In the future, I'm planning to merge stoml with the sconfig tool, and with that I will most probably redesign the use-cases and adhere to the TOML standard better.
thanks for the great work, here's a small thing to consider:
expected:
The text was updated successfully, but these errors were encountered: