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
Do not require view overrides #5990
Do not require view overrides #5990
Conversation
View overrides were removed long ago, so no need to require an empty list. The next step will be class decorators.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
😍 I spotted that one yesterday working on bye bye spree.
I'll cede the removal of the decorators to you, as a humble recognition 😂 |
ehehe :-D |
any reason why we couldn't bring in spree_paypal_express? We're maintaining our own fork anyway. |
I like it to be a separate gem actually! Paypal is really an addon. Maybe we can do the opposite in this case and move what's in the decorator to the gem? |
IMO having it in the same codebase would make it much easier to deal with such an updated integration. Remember we went through this summer. A separate gem makes sense for a product like Spree but I'm not that sure for something like OFN after Spree is merged in. |
yeah, it's debatable. Spree is a heavily customized core dependency, doesnt make sense to have it externalized 👍 Paypal is totally different case, I think it's ok to have it as a gem. I am ok with merging it to ofn. But only if integrated in a specific engine, I'd even prefer to have an engine only for it. |
makes sense in an engine, def. |
What? Why?
View overrides were removed long ago, so no need to require an empty list.
The next step will be class decorators.
What should we test?
A green build is enough.
Release notes
Do not require long gone view overrides
Changelog Category: Removed