Meta gem for recommended dependencies #739
Closed
Conversation
This file contains 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
|
After discussing with @jnunemaker, we decided adding another gem is not the way to solve the too many gems problem. Going in a different direction. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This packages up the recommended gems (
flipper,flipper-active_record, andflipper-cloud) into one meta gem so people don't have to add multiple gems (and make decisions about each one) to their Gemfile. What better way to solve the "too many gems" problem than to introduce one more, right? 🤣Each of these gems already configures itself with Rails, so nothing else should be needed to make it work.
flipper-cloudis a noop ifFLIPPER_CLOUD_TOKENis not set.Note: I'm hoping to acquire the deprecated flipper-rails gem, but open to other name ideas.