Skip to content
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

chore(linting): ignore generated css #2445

Closed
wants to merge 8 commits into from
Closed

Conversation

Haroenv
Copy link
Contributor

@Haroenv Haroenv commented Oct 4, 2017

fixes #2443

There's a bunch of sass issues we should fix, or change the rules, feel free to contribute to this PR

fixes #2443

Does this fix your issue @samouss?
@Haroenv Haroenv requested a review from samouss October 4, 2017 07:33
@samouss
Copy link
Contributor

samouss commented Oct 4, 2017

Yes but we should avoid to pass options to the CLI.

There is a .sass-lint.yml config file in the project root it will be better to handle all the
configuration inside.

@algobot
Copy link
Contributor

algobot commented Oct 4, 2017

Deploy preview ready!

Built with commit 19f285a

https://deploy-preview-2445--algolia-instantsearch.netlify.com

@Haroenv
Copy link
Contributor Author

Haroenv commented Oct 4, 2017

oops, didn't see that 😂

@Haroenv
Copy link
Contributor Author

Haroenv commented Oct 4, 2017

better like this @samouss ?

@samouss
Copy link
Contributor

samouss commented Oct 4, 2017

Yes it's perfect! But there are a lot of errors in the docgen folder (the CI failed).

We should fix it and ignore some of the vendor files (ex: bootstrap).

@@ -68,7 +63,7 @@ rules:
empty-args: 1
hex-length: 0
hex-notation:
- 2
- 1
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is this value for? To reduce the criticality?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, it used to be an error, but a warning is better in this case, because we need to solve all the warnings, and I don't want to do it in this PR

@Haroenv Haroenv added ready and removed in progress labels Nov 1, 2017
@bobylito
Copy link
Contributor

bobylito commented Nov 9, 2017

What's the status on this @Haroenv?

@Haroenv
Copy link
Contributor Author

Haroenv commented Nov 9, 2017

that it should be merged @bobylito

@Haroenv
Copy link
Contributor Author

Haroenv commented Nov 9, 2017

@bobylito the CI is complaining about the commit format of the really old commits (initial commit etc.), did that always happen?

@bobylito
Copy link
Contributor

bobylito commented Nov 9, 2017

that it should be merged @bobylito

Well I don't agree on lowering the criticality of lint checks because we don't have time to handle them. Don't we have a fix option to be able to fix this kind of problem automatically?

@bobylito the CI is complaining about the commit format of the really old commits (initial commit etc.), did that always happen?

It should not I'll have a look.

@bobylito
Copy link
Contributor

bobylito commented Nov 9, 2017

I guess the best would be to start again from a new branch forked from develop, cherry pick the changes and reopen the PR.

Haroenv added a commit that referenced this pull request Nov 9, 2017
ignore correct things now
make hex rule a warning for now because we aren't consistent with it, we can fix it later when we want less warnings

closes #2445
@Haroenv
Copy link
Contributor Author

Haroenv commented Nov 9, 2017

closing in favour of #2566

@Haroenv Haroenv closed this Nov 9, 2017
@Haroenv Haroenv deleted the chore/sass-ignore branch November 9, 2017 10:20
bobylito pushed a commit that referenced this pull request Nov 20, 2017
* chore(linting): target correct folder
ignore correct things now
make hex rule a warning for now because we aren't consistent with it, we can fix it later when we want less warnings

closes #2445

* chore(sass-lint): update rules based on our usage

* chore(scss): update files based on current rules

There are still two kinds of lint errors that I'm not sure about. I'm
not really in favor of forcing the nesting all the time. And not using
qualifying elements can have unforeseen issues.

* chore(theme): fix sass-lint errors

* chore(style): enable empty-line-between-blocks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Avoid linting the generated documentation
4 participants