-
-
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
Update support to latest requirements for extensions #177
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -42,7 +42,7 @@ If you have an existing extension and want to update it to use the latest standa | |
you can run the following in the extension's directory: | ||
|
||
```console | ||
$ solidus extension . | ||
$ bundle exec solidus extension . | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thanks for clarifying this! I think we may want to also clarify in the section above on generating a new extension, that this gem needs to be installed globally (i.e. |
||
``` | ||
|
||
In case of conflicting files, you will be prompted for an action. You can overwrite the files with | ||
|
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.
One thing we've noticed on
solidus_taxjar
when we removed Rails from theGemfile
is that it exposed an issue upstream withactive_storage
. It is explicitly required here however it isn't listed as one of the Rials gems that are dependencies ofcore
here. I still think this change is good, however if you see failures booting the dummy app, this could be the culprit. I believe this should be fixed upstream in core however.