Andrea Longhi

[API] empty cart endpoint raises 500 error with shipped order

2

**Solidus Version**: all, including master **How to reproduce** Trying to `empty` a shipped order via API raises a 500 error, which is something we should try to avoid. This can...

Rename Order#ensure_updated_shipments method

6

**Description** The naming of this method is confusing and it may induce developers to believe it refreshes shipments while it actually only destroys them on a standard Solidus store. The...

[Admin] Unsupported use of can? with array of actions

1

**Solidus Version**: all including master **Description** In some views we're probably using `cancancan` in an unsupported way. Instead of passing a single action, we provide an array with multiple values....

**Solidus Version**: all, including master **To Reproduce** Please check the attached video: https://www.loom.com/share/ad878419beab485c84deb35c13a3413d Add an item to the cart, and then push the `Empty Cart` button. All items will be...

In the admin area, [we changed](https://github.com/solidusio/solidus/blame/7e0a386f4345629829dc47b4049100667dccab4f/backend/app/views/spree/admin/orders/index.html.erb#L10) the permission check for being able to create a blank new order (i.e. show the new order button) from `:create` to `:manage`. The underlying...

Add frontend customer orders page

12

The code is basically a cut & paste of the relevant parts from the gem solidus_auth_devise. The rationale for this change is that the orders history page better belongs inside...

Unify `Spree::User` and `Spree::Order` email validation

3

_(not sure if this is more a bug or a new feature... I'm going for the latter as I think the solution will end up being a new feature 😄...

Change order state to `merged` instead of destroying it when merging orders

28

**Description** This is an (opinionated, see later) attempt at https://github.com/solidusio/solidus/issues/1449. Destroying orders when merging them is not ideal, as we lose the ability to debug what happened, which may be...

Check type before sending `#value` message to predicate

5

Closes https://github.com/activerecord-hackery/ransack/issues/1467 The previous implementation was giving for granted that every predicate respond to `#value`, which doesn't seem to be the case at least when having a `Arel::SelectManager`. by simply...

I'm experiencing this issue starting from Ransack 3.2 which removes the support for Rails 6 and some ancillary code. The issue is happening [here](https://github.com/activerecord-hackery/ransack/blob/main/lib/ransack/nodes/condition.rb#L342) and is caused by the fact...