Pascal Kaufmann

Okay, i have many requests to make this perfect: Keep the same naming of deletion mutation, thus the mutation should be called removeUser. That mutation already exists and it should...

@Mikearaya only those related entities belonging to an order in status open/null (= carts)

Currently "orders.delete" looks like this and is currently only triggered through removeOrder mutation which checks first if it's a cart or not.: delete: async (orderId) => { const deletedCount =...

ups, didn't want to close. i just had one more remark coming to my mind about this and our discussion on basecamp: If a user to be deleted (no matter...

@Mikearaya Went missing: - Removing order positions of carts that get removed (i did that already in my last commit on this branch) - Removing payment credentials of user ->...

Of course i'm doing some artifical request here but still the effect is dramatic the more objects there are in the response: Response time of that API Request above with...

much better !!

This shaves off another few milliseconds btw: ```js //const promises = Promise.all(Object.entries(object).map(async ([key, value]) => { // resolvedObject[key] = await value; //})); const promises = Promise.all(Object.keys(object).map(async (key) => { resolvedObject[key]...

Similarily, it would be awesome to extend that "locking" to pages in general, allowing the developers to lock a certain page so it cannot be removed by "marketing" people because...

Notifications should answer: - How does Messaging work? (Explain that a message is a work item that then gets transformed to some messaging plugin-specific channel like twilio, email, ...) -...