Add NextRails.current? method#174
Merged
etagwerker merged 1 commit intomainfrom Apr 1, 2026
Merged
Conversation
JuanVqz
force-pushed
the
feature/current-method
branch
from
bb675df to
0d160bc
Compare
Inverse of NextRails.next?, returns true when the application is running with the current set of dependencies. Closes #173.
JuanVqz
force-pushed
the
feature/current-method
branch
from
0d160bc to
d495dc4
Compare
etagwerker
approved these changes
Apr 1, 2026
Member
etagwerker
left a comment
etagwerker
left a comment
There was a problem hiding this comment.
@JuanVqz Looks good, thanks!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #173.
Description
Adds
NextRails.current?as a convenience method that returns!NextRails.next?.This makes conditional logic in dual-boot setups more readable when targeting
the current dependencies.
Motivation and Context
Requested in #173 — having the inverse of
NextRails.next?avoids negationin application code and improves readability.
How Has This Been Tested?
NextRails.current?covering: BUNDLE_GEMFILE unset,set to
Gemfile.next, and set to something elsebundle exec rspec spec/next_rails_spec.rbI will abide by the code of conduct