Skip to content

Update README.md#169

Draft
JuanVqz wants to merge 1 commit intomainfrom
chore/improve-readme
Draft

Update README.md#169
JuanVqz wants to merge 1 commit intomainfrom
chore/improve-readme

Conversation

@JuanVqz
Copy link
Member

@JuanVqz JuanVqz commented Mar 20, 2026

Description

Motivation and Context

I think our README.md looks patched, and needed a bit of ❤️

How Has This Been Tested?

I rendered the README.md in my editor and it looked good.

I will abide by the code of conduct

@JuanVqz JuanVqz requested review from arielj and etagwerker March 20, 2026 00:13
Add this line to your application's Gemfile:

> These scripts are still early days and may not work in every environment or app.
> **Note:** If you add this gem to a group, make sure it is the `test` env group.
Copy link
Member

Choose a reason for hiding this comment

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

I don't quite agree with this.

I've been using next_rails without a group in the Gemfile because it makes it easier to call NextRails.next? anywhere in the codebase.

> better fit your environment.
```ruby
gem 'next_rails'
```
Copy link
Member

Choose a reason for hiding this comment

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

I highly recommend adding it to your Gemfile like this. ☝🏻

# Find minimum compatible ruby version with Rails 7.0.0
bundle_report ruby_check --rails-version=7.0.0
# Edit your Gemfile to conditionally set gem versions using `next?`
vim Gemfile
Copy link
Member

Choose a reason for hiding this comment

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

Maybe mention that the init command will add a definition of next? to the top of the Gemfile?

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.

2 participants