-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Test app task: Allow passing in user class #5956
Conversation
Without this, every extension's test app always has `Spree::LegacyUser` configured. Mostly, that's fine, but for solidus_auth_devise, it'd be nicer if the generated spree.rb file would have `Spree.user_class = "Spree::User"` rather than `Spree::LegacyUser`.
77d7ada
to
520efc0
Compare
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.
Makes sense. Thank you
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #5956 +/- ##
=======================================
Coverage 87.81% 87.81%
=======================================
Files 476 476
Lines 11656 11656
=======================================
Hits 10236 10236
Misses 1420 1420 ☔ View full report in Codecov by Sentry. |
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.
Makes sense, thanks Martin!
I'd like to use this to get extensions to use the new loading mechanism from Flickwerk, and extensions are always tested against many Solidus versions. Can I have this backported to Solidus 4.0 - 4.4? |
💔 Some backports could not be created
Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
💔 Some backports could not be created
Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
Without this, every extension's test app always has
Spree::LegacyUser
configured. Mostly, that's fine, but for solidus_auth_devise, it'd be nicer if the generated spree.rb file would haveSpree.user_class = "Spree::User"
rather thanSpree::LegacyUser
.See this spec failure as an example of what I mean :) solidusio/solidus_auth_devise@7478697#diff-8d002d054349f039bafc03785a785a1594ef6b4539298f59e84e95217a97abedR21
Checklist
Check out our PR guidelines for more details.
The following are mandatory for all PRs:
The following are not always needed: