Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Move our recommended configs into a file that can be inherited #76

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 3 commits into from
Jun 9, 2023

Conversation

khiga8
Copy link
Collaborator

@khiga8 khiga8 commented Jun 9, 2023

Fixes: #77

I discovered this inherit_gem functionality exists upon diving into the erb-lint codebase! This lets consumers pull in the lint configs we define.

This was not documented in the README and there aren't any custom erb-lint libraries out there, so we never knew this was possible.

This update will help ensure that consumers can pull in configuration we recommend when they bump this gem up.

While we can automatically inherit the specified configs, the custom rules are not automatically registered, so we still need the consumer to require it by creating a file in .erb-linters/some_ruby_file.rb and requiring our rules.

README.md Outdated

``` ruby
gem "erb_lint", require: false
gem "erblint-github"
```

2. Require the linters within the `.erb-linters` folder. This could be done by adding a file `.erb-linters/erblint-github.rb` with the following line.
2. **Important**: Create a new file with the path `.erb-linters/erblint-github.rb` and add the line:
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

It'd be nice to eventually get rid of this step. I believe this requires updates to erb-lint.

@khiga8 khiga8 force-pushed the kh-inherit-config branch from c8b287e to 7918872 Compare June 9, 2023 01:04
@khiga8 khiga8 marked this pull request as ready for review June 9, 2023 01:06
@khiga8 khiga8 requested a review from a team as a code owner June 9, 2023 01:06
@khiga8 khiga8 requested a review from accessibility-bot June 9, 2023 01:06
@accessibility-bot
Copy link

👋 Hello and thanks for pinging us! You've entered our first responder queue. An accessibility first responder will review this soon.

  • 💻 On PRs for our review: please provide a review environment with steps to validate, screenshots (with alt text), or videos demonstrating functionality we should be checking. This will help speed up our review and feedback cycle.
  • ⚠️ If this is urgent, please visit us in #accessibility on Slack and tag the first responder(s) listed in the channel topic.

@khiga8 khiga8 merged commit 42d3e51 into main Jun 9, 2023
@khiga8 khiga8 deleted the kh-inherit-config branch June 9, 2023 19:13
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.

Figure out how consumers can inherit our recommended rule configs
3 participants
Morty Proxy This is a proxified and sanitized view of the page, visit original site.