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
So for years I've used a 2-space indentation scheme because I often work on a small screen. (Don't judge me by my laptop size!) It's obvious that when indentation on an entire file changes, it is difficult to track what else has changed in that commit. I propose that I go through all the files switch them to the following standard:
Block indentation is to be 4-spaces.
Indentation follows matlab defaults except
on the first level of a classdef block there is no indentation, e.g., method and property blocks are flush left.
classdefabc% Help stringpropertiespropertyendmethodsfunction xyz(...)
...
endendend
If it makes more sense in some case not to follow this standard, then don't.
The text was updated successfully, but these errors were encountered:
So for years I've used a 2-space indentation scheme because I often work on a small screen. (Don't judge me by my laptop size!) It's obvious that when indentation on an entire file changes, it is difficult to track what else has changed in that commit. I propose that I go through all the files switch them to the following standard:
classdef
block there is no indentation, e.g.,method
andproperty
blocks are flush left.The text was updated successfully, but these errors were encountered: