Skip to content
This repository was archived by the owner on Feb 25, 2021. It is now read-only.

Conversation

@ntwb
Copy link
Collaborator

@ntwb ntwb commented Jan 22, 2016

No description provided.

Choose a reason for hiding this comment

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

Don't need to catch this. Just return promise.

Copy link
Contributor

Choose a reason for hiding this comment

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

@TrySound Do you mean like this?:

test("no warnings with valid css", t => {
  return stylelint.lint({
    code: validCss,
    config: config,
  })
  .then(data => {
    const { errored, results } = data
    const { warnings } = results[0]
    t.notOk(errored, "no errored")
    t.is(warnings.length, 0, "flags no warnings")
  })
})

I just want to double check before I update the tests in the standard and suitcss configs as well.

Choose a reason for hiding this comment

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

yep

Copy link
Contributor

Choose a reason for hiding this comment

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

@TrySound Thanks! :)

@ntwb Are you able to update the tests in this PR if I go ahead and update standard and suitcss?

Choose a reason for hiding this comment

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

Here too

@ntwb
Copy link
Collaborator Author

ntwb commented Jan 26, 2016

Thanks for the feedback and code tweaks @TrySound & @jeddy3

Apologies for not getting to this sooner 😄

package.json Outdated

Choose a reason for hiding this comment

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

There is 0.11.0 already. Update before merge please :)

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Done, thanks 👍

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I cannot work out why the Windows AppVeyor tests fail for NodeJS v5.x ¯_(ツ)_/¯

Copy link
Contributor

Choose a reason for hiding this comment

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

Can you try adding these tweaks to your appveyor file please?

I'm not sure what you think, but perhaps testing on .12, 4 and 5 is a little excessive for a config. Probably just 5 is alright?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I removed the node-modules folder from the AppVeyor cache and:

WordPress' currently supports "build tools" on each of these NodeJS versions, as such I'd like to try and keep compatibility of all these NodeJS versions for both *nix and Windows.

Choose a reason for hiding this comment

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

Yeah cache invalidating is the worst thing ever :)

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

The AppVeyor 5.x build failed again, I've restarted some builds and jobs as comparing AVA 0.11.0 AppVeyor builds I've a suspicion this could actually be an AppVeyor issue rather than ours!

Copy link
Contributor

Choose a reason for hiding this comment

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

as such I'd like to try and keep compatibility of all these NodeJS versions for both *nix and Windows.

Sgtm.

I've a suspicion this could actually be an AppVeyor issue rather than ours!

Agreed. Previously version 4 failed and 5 passed. I restarted the test a few minutes ago and 4 now passes, but 5 fails :(

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Agreed, will merge now, maybe after merging AppVeyor will settle down ¯_(ツ)_/¯

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Each of the 5.x, 4.x, and 0.12.x AppVeyor builds now pass 👍

https://ci.appveyor.com/project/stylelint/stylelint-config-wordpress/build/98

ntwb added a commit that referenced this pull request Jan 27, 2016
Use ava for tests and Stylelint 4.x
@ntwb ntwb merged commit 1f25a25 into master Jan 27, 2016
@ntwb ntwb deleted the use-ava branch January 27, 2016 09:41
ntwb pushed a commit that referenced this pull request Dec 12, 2018
## The devDependency [stylelint-find-rules](https://github.com/alexilyaev/stylelint-find-rules) was updated from `1.1.1` to `2.0.0`.
This version is **not covered** by your **current version range**.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

---

<details>
<summary>Release Notes for v2.0.0</summary>

<ul>
<li>Breaking: Minimal supported stylelint version is now 8.3.0</li>
<li>Fix: Support extends of extends (closes <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="249172069" data-permission-text="Issue title is private" data-url="alexilyaev/stylelint-find-rules#9" data-hovercard-type="issue" data-hovercard-url="/alexilyaev/stylelint-find-rules/issues/9/hovercard" href="https://urls.greenkeeper.io/alexilyaev/stylelint-find-rules/issues/9">#9</a>)</li>
<li>Chore: Added more configs that extend other configs for testing</li>
</ul>
</details>

<details>
<summary>Commits</summary>
<p>The new version differs by 8 commits.</p>
<ul>
<li><a href="https://urls.greenkeeper.io/alexilyaev/stylelint-find-rules/commit/1610628bb3d3c3ed3f8ba7c5b55285257f9aed01"><code>1610628</code></a> <code>2.0.0</code></li>
<li><a href="https://urls.greenkeeper.io/alexilyaev/stylelint-find-rules/commit/06baf0b42948aae92888207abe0bfb25f149d2dd"><code>06baf0b</code></a> <code>Merge pull request #19 from alexilyaev/support-extends</code></li>
<li><a href="https://urls.greenkeeper.io/alexilyaev/stylelint-find-rules/commit/5595e91bce12a24dcbb25b82d7041ec09cafe042"><code>5595e91</code></a> <code>Support extends of extends (closes #9)</code></li>
<li><a href="https://urls.greenkeeper.io/alexilyaev/stylelint-find-rules/commit/922c53e51ea65413e30e0e89a56b629f5bf8b50a"><code>922c53e</code></a> <code>dev: Update lint-staged</code></li>
<li><a href="https://urls.greenkeeper.io/alexilyaev/stylelint-find-rules/commit/8fdd429f81b74b74e3908c9ddf3a3f47860c9227"><code>8fdd429</code></a> <code>chore: Minor ESLint config update</code></li>
<li><a href="https://urls.greenkeeper.io/alexilyaev/stylelint-find-rules/commit/edc640fa30e693580a33bea95c2705383a926151"><code>edc640f</code></a> <code>Chore: Add missing ESLint rules</code></li>
<li><a href="https://urls.greenkeeper.io/alexilyaev/stylelint-find-rules/commit/bd6b5d73f690f1cdb3e4e52a306eeee928172f1e"><code>bd6b5d7</code></a> <code>Bump deps versions</code></li>
<li><a href="https://urls.greenkeeper.io/alexilyaev/stylelint-find-rules/commit/3bc0a2e6880c9efc444b05d6705c9c74a5ca01a0"><code>3bc0a2e</code></a> <code>Updated circleci config to 2.0</code></li>
</ul>
<p>See the <a href="https://urls.greenkeeper.io/alexilyaev/stylelint-find-rules/compare/ed029e15c6e8f67b3be3dbffe433d4956b70757c...1610628bb3d3c3ed3f8ba7c5b55285257f9aed01">full diff</a></p>
</details>

<details>
  <summary>FAQ and help</summary>

  There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
</details>

---


Your [Greenkeeper](https://greenkeeper.io) bot 🌴
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.

4 participants