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

Remove responders dependency from core #2090

Merged
merged 1 commit into from
Jul 21, 2017

Conversation

cbrunsdon
Copy link
Contributor

Moves the responders dependency to the API, the place where we actually use it.

I'll rebase this once #1956 is merged, I just want to run tests.

We've removed the responders code from core, so the only thing that is
using the responders gem is inside the api now
@cbrunsdon cbrunsdon force-pushed the remove_responder_from_core branch from 17499ed to 1850853 Compare July 18, 2017 20:14
@cbrunsdon
Copy link
Contributor Author

Okay with #1956 gone this is good to go whenever someone has a sec

@jhawthorn jhawthorn changed the title Remove responder from core Remove responders dependency from core Jul 18, 2017
Copy link
Contributor

@mamhoff mamhoff left a comment

Choose a reason for hiding this comment

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

👍 LGTM!

Copy link
Member

@tvdeyen tvdeyen left a comment

Choose a reason for hiding this comment

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

Thanks

@tvdeyen tvdeyen merged commit 5f404db into solidusio:master Jul 21, 2017
@kennyadsl kennyadsl mentioned this pull request Sep 16, 2019
2 tasks
waiting-for-dev added a commit to nebulab/solidus that referenced this pull request Jun 16, 2023
We removed the responders dependency from solidus_core in
solidusio#2090. However, we forgot to
remove the use of the responders API from solidus_core. We weren't
catching this because all consumers of solidus_core's
`Spree::BaseController` had the responders gen as a dependency (see
solidusio#3336)
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.

3 participants