Skip to content
This repository has been archived by the owner on Sep 7, 2020. It is now read-only.

Update stylelint & stylelint-config-standard. (#718) #741

Merged
merged 2 commits into from
Sep 15, 2016
Merged

Update stylelint & stylelint-config-standard. (#718) #741

merged 2 commits into from
Sep 15, 2016

Conversation

ben-eb
Copy link
Contributor

@ben-eb ben-eb commented Sep 12, 2016

I've stuck with the standard configuration instead of adapting the configuration to fit the CSS, hope this is OK. 馃槃

@thangngoc89
Copy link
Contributor

@ben-eb we follow standard rule. LGTM

@MoOx
Copy link
Owner

MoOx commented Sep 13, 2016

The reference should be edited in all places:

  • package.json devDeps
  • package.json optionalPeerDeps
  • docs/package.json

@@ -1,6 +1,6 @@
.banner {
position: fixed;
position: sticky;
position: sticky; /* stylelint-disable-line */
Copy link
Owner

Choose a reason for hiding this comment

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

what is the problem here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It's a duplicate declaration, Stylelint would prefer that either fixed or sticky was specified, not both.

Copy link
Owner

Choose a reason for hiding this comment

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

Hummmm ok... Not sure if that make total sense to get this in the "standard" config since this kind of tricks are handy when you work with CSS but I guess it's not a big deal for us... poke @davidtheclark @jeddy3

Copy link
Contributor Author

@ben-eb ben-eb Sep 14, 2016

Choose a reason for hiding this comment

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

I've stuck with the standard configuration instead of adapting the configuration to fit the CSS

馃槈

Copy link

Choose a reason for hiding this comment

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

Hello. I hadn't considered that use case when enabling the declaration-block-no-duplicate-properties rule. I had assumed all fallbacks would be handled by tooling.

There's an appropriate option that to make the rule more permissive for this situation: ignore: ["consecutive-duplicates-with-different-values"].

I've created an issue to discuss using that option by default in the standard config.

Copy link
Owner

Choose a reason for hiding this comment

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

@jeddy3 thanks for your input!

@thangngoc89
Copy link
Contributor

This should close #647 as well

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants