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

Remove no-continue rule #71

Closed
DHedgecock opened this issue May 27, 2019 · 1 comment · Fixed by #87
Closed

Remove no-continue rule #71

DHedgecock opened this issue May 27, 2019 · 1 comment · Fixed by #87

Comments

@DHedgecock
Copy link
Member

Summary

Allow using language features of the language we're writing 😑

DHedgecock added a commit that referenced this issue Jul 12, 2019
This "fixes" a few of the Airbnb rule values that I would argue are totally fine. Using continue
makes sense in some cases, and files with only named exports is a great practice for utility
modules.

Closes #70, Closes #71
DHedgecock added a commit that referenced this issue Jul 12, 2019
This "fixes" a few of the Airbnb rule values that I would argue are totally fine. Using continue
makes sense in some cases, and files with only named exports is a great practice for utility
modules.

Closes #70, Closes #71
DHedgecock pushed a commit that referenced this issue Jul 12, 2019
## [12.0.1](v12.0.0...v12.0.1) (2019-07-12)

### Docs

* Fix changelog docs and update to latest dev deps 🔧 (#86) ([c870732](c870732)), closes [#86](#86)

### Fix

* Fix import and continue rule definitions ✨ (#87) ([0948beb](0948beb)), closes [#87](#87) [#70](#70) [#71](#71)
@DHedgecock
Copy link
Member Author

🎉 This issue has been resolved in version 12.0.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Successfully merging a pull request may close this issue.

1 participant