Skip to content

update no-unknown-modifier rules, resolve #107 #109

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

Merged
merged 2 commits into from
May 26, 2016
Merged

update no-unknown-modifier rules, resolve #107 #109

merged 2 commits into from
May 26, 2016

Conversation

cgcgbcbc
Copy link
Contributor

@cgcgbcbc cgcgbcbc commented May 16, 2016

add always, failing modifier. resolve #107

@jamestalmage
Copy link
Contributor

#102 already covers always (I just merged it).

You need to rebase, and drop the always related stuff.

@cgcgbcbc
Copy link
Contributor Author

@jamestalmage rebased

@jamestalmage
Copy link
Contributor

LGTM!

We will wait for avajs/ava#831 to land before merging.

Thanks @cgcgbcbc!

@jfmengels
Copy link
Contributor

LGTM, thanks @cgcgbcbc :)

@sindresorhus sindresorhus merged commit 4558f23 into avajs:master May 26, 2016
@jamestalmage
Copy link
Contributor

Somebody should write a bot that would notify you in this thread, when the thread you are watching gets closed / merged.

Would have been better to merge this right after #831 landed so we weren't risking making the contributor rebase (he didn't end up having to, which is good, but it would be annoying if he did because we just forgot this was sitting here).

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.

Update no-unknown-modifiers rule to accept failing and always modifier
4 participants