solidus_dev_support icon indicating copy to clipboard operation
solidus_dev_support copied to clipboard

A collection of tools for developing Solidus extensions.

Results 18 solidus_dev_support issues
Sort by recently updated
recently updated
newest added

## Summary Those changes are sourced from adjustments done on individual extensions. ## Checklist Check out our [PR guidelines](https://github.com/solidusio/.github/blob/master/CONTRIBUTING.md#pull-request-guidelines) for more details. The following are mandatory for all PRs: -...

needs changelog label

## Summary Updated Readme with more explicit shell command for running `solidus extension .` Removed `rails > 0.a`, bundler has been patched to prevent the issue with resolving dependencies. Bumped...

enhancement
infrastructure

**Desired Behavior** Let dev-support help with extensions that work with solidus_starter_frontend. - Switch to a lightweight release process (use bundler gem tasks and GitHub releases) - Setup scripts for generating,...

enhancement

It would be a simple API call, using the same token as before, and the contents can be reused for both the changelog and the release. - Let's also update...

What about removing `test_files`? See https://github.com/rubocop/rubocop/issues/10675 _Originally posted by @waiting-for-dev in https://github.com/solidusio/solidus_paypal_braintree/pull/339#discussion_r1041763281_

Solidus will soon have a 3.0 version. We should allow gemspec of the extension template to support Solidus 3 as well. Also, we can change the Ruby version to allow...

I'd like to have an automated way to cleanup legacy files when the generator runs, e.g. https://github.com/solidusio/solidus_dev_support/pull/118.

Using `solidus` as the executable name makes little sense for a gem called `solidus_dev_support`, we should establish a base `solidus` command within core and allow it to be extended by...

An extension without assets will fail specs because the `test_app` is always created requiring the assets (even if they don't exist). ``` Running extension installation generator... append vendor/assets/javascripts/spree/frontend/all.js append vendor/assets/javascripts/spree/backend/all.js...

It would be useful to have an override generator that creates the right placeholder module in the right path.