Home Dashboard Directory Help
Search

.less: indentation is weird by spongman


Status: 

Closed
 as External Help for as External


2
0
Sign in
to vote
Type: Bug
ID: 808116
Opened: 11/8/2013 1:13:29 PM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

the indenting of selectors in .less files is messed up.
Details
Sign in to post a comment.
Posted by JulienBérubé on 1/29/2014 at 12:18 PM
The problem still exists.
The "hierarchical indentation" setting mentioned below exists only for CSS, not LESS.

For instance:
#photopicker-selection.edit-mode {
    span.drop-icon {
        cursor: pointer;

        div.icon-drop-thumb {
            height: 30px;
        }
    }

    span.drop-icon:hover {
        border: solid 2px @brand-primary;
    }
}
Will be autoindented to:
#photopicker-selection.edit-mode {
    span.drop-icon {
        cursor: pointer;

        div.icon-drop-thumb {
            height: 30px;
        }
    }

        span.drop-icon:hover {
            border: solid 2px @brand-primary;
        }
}

Style span.drop-icon:hover get over indented, giving the impression that some closing brace is missing after it.
Posted by spongman on 11/26/2013 at 5:38 PM
there is no such setting for .less files.

please re-open. this is still a bug.
Posted by Microsoft on 11/26/2013 at 2:59 PM
Thanks for the feedback. This is called "hierarchical indentation" and can be controlled through the settings.
Posted by Microsoft on 11/26/2013 at 2:58 PM
Thanks for the feedback. This is called "hierarchical indentation" and can be controlled through the settings.
Posted by Microsoft on 11/11/2013 at 12:28 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Microsoft on 11/8/2013 at 1:50 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.