-
Notifications
You must be signed in to change notification settings - Fork 49
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
Bug/Request: Single line alignment of VALUE Expressions with BASE/FOR #170
Comments
Hi Ludwig, you're right, this was previously kept on one line, but unintentionally (see #154): the option "Table rows: Keep multiple components on single line" did more than it was meant to do. But I do see your point – maybe we just need a dedicated option for these cases… Kind regards, |
Hi Jörg-Michael, a new option sounds good 😊. Kind regards, |
Hi Ludwig, with the next release, you will find the following new option in the rule "Align parameters and components": For "Never", you get: For "Always" or "If maximum line length A is observed", the code on the left-hand side is preserved. This is then similar to the behavior before version 1.8.0, but a bit stricter, requiring line length A (default: 120 chars) to be observed instead of line length B (default: 160 chars). Kind regards, |
Hi Jörg-Michael, thanks a lot 😊👍🏻. Kind regards, |
Hi Ludwig, thanks for opening this issue – the new option is now available with version 1.13.0, which was just released! Kind regards, |
Hi,
in an an earlier version - I think before 1.8.0 - small short VALUE expressions that used BASE or FOR were usually kept in one line. Now they are always put into 2 lines.
The following snippet:
... is formatted into this in the current version:
If this change is because of some clean code rule, I would like the option that such short assignment are kept in one line.
If it's a bug, then please fix it.
Thanks and Regards,
Ludwig
The text was updated successfully, but these errors were encountered: