Is it possible to prevent formatting of short lines - regardless of number of attributes? about xamlstyler HOT 2 OPEN

We've declined requests in the past for column break rules (#12), since while column break rules might work for most languages, we did not believe it made as much sense for a markup language like XAML that make use of heavy nested elements, but if this new setting was based on element length (and not line length), that starts to feel to me like a consistent alternative to Max Attribute Characters Per Line.

What are your thoughts on conflict resolution behavior between this new proposed setting and Max Attribute Characters Per Line?

from xamlstyler.

What are your thoughts on conflict resolution behavior between this new proposed setting and Max Attribute Characters Per Line?

I would have this new setting take priority over MACPL as it considers the element as a whole, rather than just a subset. Actually, I would have this new setting override all (I think--but I haven't double-checked) other settings.
What I want from this option is the ability to say something equivalent to "in this specific situation, do this specific thing, but if this situation is not met, then follow the existing rules."
Having a new setting related to overall element length work in combination with other, existing settings would increase the complexity of the internal code as well as make it harder to reason over what results different combinations of settings will produce.
As a completely separate new setting, this also avoids any unexpected confusion and complication by possibly changing existing settings/behavior.

This new setting should default to a value of -1 and only be considered if greater than 0. (Yes, even though there's a theoretical minimal size of 13 before it could have a meaningful/useful effect.)

While I'm only proposing a single new setting that takes priority over all others, I recognize that this sets a precedent for potentially adding others in the future and that having multiple settings that each take priority over general settings introduces other challenges. I don't believe this should be a blocker, though, as there are ways of prioritizing multiple settings that may take priority, and these can be applied as and when this becomes a factor.

from xamlstyler.