-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
Fix loading factories in extensions after the last changes in Solidus #169
Conversation
It looks like this PR is missing a label to determine the type of change it introduces. The maintainer should add one of the following labels:
Additionally, the maintainer may also want to add one of the following:
Once the correct labels have been set, simply remove the |
Specs failures are legit, until we merge the PR on Solidus mentioned above. |
5bae9d8
to
b5c1095
Compare
This commit reflects the last changes we made in Solidus to support the new FactoryBot loading mechanism. When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`.
b5c1095
to
68b6496
Compare
I didn't expect that. 🤔 |
No problem, this gem is mainly used from Rubygems so it does nothing until we release a new version, which is actually how all the other gems should work as well. 😬 |
This commit reflects changes made by Solidus [PR #169](solidusio/solidus_dev_support#169 (comment)) When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`.
This commit reflects changes made by Solidus [PR #169](solidusio/solidus_dev_support#169 (comment)) When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`.
This commit reflects changes made by Solidus [PR #169] (solidusio/solidus_dev_support#169 (comment)) When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`. Additionally, this extention makes use of assertions (i.e. `assert_nothing_raised) found in the version of Rails not used by Solidus 2.10, therefore it must be manually configured in `Rspec.config`.
This commit reflects changes made by Solidus [PR #169] (solidusio/solidus_dev_support#169 (comment)) When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`. Additionally, this extention makes use of assertions (i.e. `assert_nothing_raised) found in the version of Rails not used by Solidus 2.10, therefore it must be manually configured in `Rspec.config`.
This commit reflects changes made by Solidus [PR #169](solidusio/solidus_dev_support#169 (comment)) When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`.
This commit reflects changes made by Solidus [PR #169] (solidusio/solidus_dev_support#169 (comment)) When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`. Additionally, this extention makes use of assertions (i.e. `assert_nothing_raised) found in the version of Rails not used by Solidus 2.10, therefore it must be manually configured in `Rspec.config`.
This commit reflects changes made by Solidus [PR solidusio-contrib#169] (solidusio/solidus_dev_support#169 (comment)) When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`. Additionally, this extention makes use of assertions (i.e. `assert_nothing_raised) found in the version of Rails not used by Solidus 2.10, therefore it must be manually configured in `Rspec.config`.
This commit reflects changes made by Solidus [PR #169] (solidusio/solidus_dev_support#169 (comment)) When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`. Additionally, this extention makes use of assertions (i.e. `assert_nothing_raised) found in the version of Rails not used by Solidus 2.10, therefore it must be manually configured in `Rspec.config`.
This commit reflects changes made by Solidus [PR #169] (solidusio/solidus_dev_support#169 (comment)) When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`. Additionally, this extention makes use of assertions (i.e. `assert_nothing_raised) found in the version of Rails not used by Solidus 2.10, therefore it must be manually configured in `Rspec.config`.
This commit reflects changes made by Solidus [PR #169] (solidusio/solidus_dev_support#169 (comment)) When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`. Additionally, this extention makes use of assertions (i.e. `assert_nothing_raised) found in the version of Rails not used by Solidus 2.10, therefore it must be manually configured in `Rspec.config`.
This commit reflects changes made by Solidus [PR #169](solidusio/solidus_dev_support#169 (comment)) When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`.
This commit reflects changes made by Solidus [PR #169] (solidusio/solidus_dev_support#169 (comment)) When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`.
This commit reflects changes made by Solidus [PR #169] (solidusio/solidus_dev_support#169 (comment)) When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`. Additionally, this extention makes use of assertions (i.e. `assert_nothing_raised) found in the version of Rails not used by Solidus 2.10, therefore it must be manually configured in `Rspec.config`.
This commit reflects changes made by Solidus [PR #169] (solidusio/solidus_dev_support#169 (comment)) When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`.
This commit reflects changes made by Solidus [PR #169] (solidusio/solidus_dev_support#169 (comment)) When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`.
This commit reflects changes made by Solidus [PR #169] (solidusio/solidus_dev_support#169 (comment)) When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`. Additionally, this extention makes use of assertions (i.e. `assert_nothing_raised) found in the version of Rails not used by Solidus 2.10, therefore it must be manually configured in `Rspec.config`.
This commit reflects changes made by Solidus [PR #169](solidusio/solidus_dev_support#169 (comment)) When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`.
This commit reflects changes made by Solidus [PR #169] (solidusio/solidus_dev_support#169 (comment)) When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`.
This commit reflects changes made by Solidus [PR #169] (solidusio/solidus_dev_support#169 (comment)) When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`.
This commit reflects changes made by Solidus [PR #169] (solidusio/solidus_dev_support#169 (comment)) When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`.
This commit reflects changes made by Solidus [PR #169] (solidusio/solidus_dev_support#169 (comment)) When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`.
This commit reflects changes made by Solidus [PR #169] (solidusio/solidus_dev_support#169 (comment)). When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`.
This commit reflects changes made by Solidus [PR solidusio#169] (solidusio/solidus_dev_support#169 (comment)) When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`.
This commit reflects changes made by Solidus [PR #169] (solidusio/solidus_dev_support#169 (comment)) When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`.
This commit reflects changes made by Solidus [PR #169] (solidusio/solidus_dev_support#169 (comment)) When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`.
This commit reflects changes made by Solidus [PR #169] (solidusio/solidus_dev_support#169 (comment)) When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`.
This commit reflects changes made by Solidus [PR #169] (solidusio/solidus_dev_support#169 (comment)) When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`.
This commit reflects changes made by Solidus [PR #169] (solidusio/solidus_dev_support#169 (comment)) When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`.
This commit reflects changes made by Solidus [PR #169] (solidusio/solidus_dev_support#169 (comment)) When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`.
This commit reflects changes made by Solidus [PR #169] (solidusio/solidus_dev_support#169 (comment)) When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`.
This commit reflects changes made by Solidus [PR #169] (solidusio/solidus_dev_support#169) When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`.
This commit reflects changes made by Solidus [PR #169] (solidusio/solidus_dev_support#169) When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`.
This commit reflects changes made by Solidus [PR #169] (solidusio/solidus_dev_support#169) When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`.
This commit reflects changes made by Solidus [PR #169] (solidusio/solidus_dev_support#169) When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`.
This commit reflects changes made by Solidus [PR solidusio#169] (solidusio/solidus_dev_support#169 (comment)) When testing extensions using Solidus vesions that support the definition_file_paths, it will load the core factory first and then the ones defined in `lib/extension_name/testing_support/factories`.
Summary
This PR reflects the last changes we made in Solidus to support the new FactoryBot loading mechanism.
We need to merge and release new versions of Solidus after solidusio/solidus#3907, merge this PR and release a new version of
solidus_dev_support
to have the ecosystem working again with factories.When testing extensions using Solidus versions that support the
definition_file_paths
, it will load the core factory firstand then the ones defined in
lib/extension_name/testing_support/factories
.If the extension has a
lib/extension_name/testing_support/factories.rb
file that loads all the factories intolib/extension_name/testing_support/factories/
, it should be removed now. If that happens this PR will make it print a deprecation warning telling users what to do.Checklist
[ ] I have added relevant automated tests for this change.