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

Removed spring from Gemfile, moved poltergeist and quiet_assets to groups #2804

Closed
wants to merge 1 commit into from

Conversation

parndt
Copy link
Member

@parndt parndt commented Dec 10, 2014

Spring still works just fine for me if I put it in .gemfile which
is a file that we have for installing gems according to each developer's
preference. If I completely uninstall Spring from my system then it
still works to invoke every command that asks for Spring due to
Spring rescuring from LoadError.

If I then place Spring back in .gemfile it will figure out that it
is now present and will load, speeding up subsequent invocations.

…oups.

Spring still works just fine for me if I put it in .gemfile which
is a file that we have for installing gems according to each developer's
preference.  If I completely uninstall Spring from my system then it
still works to invoke every command that asks for Spring due to
Spring rescuring from LoadError.

If I then place Spring back in .gemfile it will figure out that it
is now present and will load, speeding up subsequent invocations.
gem 'spring'
gem 'spring-commands-rspec'
gem 'poltergeist'
gem 'quiet_assets', group: :development
Copy link
Contributor

Choose a reason for hiding this comment

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

The test group is a block so I think it would make sense for the development group to be a block even though there's only one item in it. Either way I think it would be better to have the development gems separate from the production gems, so move this to between the database config conditions and the test group.

Copy link
Member Author

Choose a reason for hiding this comment

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

Technically there are no production gems, given this is never run in production ;)

Copy link
Contributor

Choose a reason for hiding this comment

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

True :P

@parndt parndt closed this Dec 18, 2014
@parndt parndt deleted the remove-spring-move-poltergeist-to-test branch July 18, 2015 03:52
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.

None yet

2 participants