Replies: 1 comment 4 replies
-
I don't have a strong opinion on this. The generated script is still readable even with the inconsistent indentation. Most of the time I'm reading the code under `src` anyway, not the code in the build artifact.
I lean toward waiting for a feature request from a user with a well-defined rationale. Unless it's extremely trivial to implement without making things more complex.
Side note: Might be worth thinking about how multi-line strings are handled. Adding ANY indentation to those can cause problems. I have learned to work around that personally.
Ex:
```
foo='
bar
'
```
gets transformed into:
```
foo='
bar
'
```
which adds spaces in front of "bar", so my string has been unexpectedly changed.
But handling that also sounds really complex, so it's something I'm happy to work around. I'd actually rather not add any indentation at all.
|
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I noticed people (@pcrockett) using 4 space indentation in their own code, which creates an inconsistent script since bashly itself indents with 2 spaces.
Should there be a setting for it?
If we do this, we will probably be able to get rid of the "spaces to tabs" conversion done when users choose tab character indentation, and instead have the
String#indent
extension itself worry about the indentation character natively and at the source.Beta Was this translation helpful? Give feedback.
All reactions