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
{{ message }}
This repository has been archived by the owner on Oct 16, 2021. It is now read-only.
I use eclint for coding style validation. eclint generates an error, if leading spaces. I need remove leading spaces manually. It may take a lot of time.
3. Steps to reproduce
I open any SashaLeadingSpaces.css file → I print c- → I select c-long Long Comment in autocomplete.
I understand your approach but it seems more like a preference and a configuration of your environment than a feature or a bug on the snippets themselves, I'm trying to keep them consistent and flexible.
A change in the eclint settings would be prefered here as this is more suited to preferences than to features.
1. Summary
It would be nice, if would be possible use comments without leading spaces in lines.
2. Argumentation
I preferred tabs, not spaces indentation.
I use eclint for coding style validation. eclint generates an error, if leading spaces. I need remove leading spaces manually. It may take a lot of time.
3. Steps to reproduce
I open any
SashaLeadingSpaces.css
file → I printc-
→ I selectc-long Long Comment
in autocomplete.4. Expected behavior
eclint no generate errors.
5. Actual behavior
Thanks.
The text was updated successfully, but these errors were encountered: