Pascal Kaufmann
Pascal Kaufmann
Currently Unchained creates or reuses an existing OrderDelivery when "setOrderDeliveryProvider" is used. So you can't even do the upper mutation because you don't know the correct orderDeliveryId until you have...
We got another issue with a new case also conflicting with the current concept. It basically boils down to the problem that in order to get a list of pickup...
Very interesting topic but I think we still haven't found a sustainable way to tackle these problems yet. I agree with the requirements: - As a shop admin I want...
More important than I though, just ran into an issue where the removal of a currency made price queries crashing
- [x] Currently Assortments have no deletion flags, should they have? - [x] Users don’t support deletion, another issue
Partly implemented, see above, so we postponed this to Unchained 2.0
The solution we are proposing regarding that matter will be the introduction of a user delete method and mutation which will essentially: - Mark user as deleted - Keep userId...
Okay, after discussion with @Mikearaya we do this in 2 steps: 1. Phase: Simple Deleted Flag - Keep User as is with all data, but set DELETED status - Rename...
I have reproduced this by doing an infinite loop with assortment children: - Add Assortment Test1 - Add Assortment Test2 - Go to Test1, add Test2 as Subassortment - Go...
Basically, you will need to add a check and a custom error when somebody tries to add an assortment link that would end up in a cycle