Michael Bromley

The solution here would be to remove the unique constraint at the DB level and do a check for uniqueness among non-deleted rows, like we already do with Customer entitities.

Since v1.6 we can remove the unique constraint at the database level using the following metadata modifier: ```ts import { Administrator, EntityMetadataModifier } from '@vendure/core'; import { Column } from...

Hi, could you include all the info you shared in the slack chat - the code for your auth strategy and then the resulting rows in your db tables?

Thanks for taking the time to create the repo. The problem is that the `identifier` field should match the email address: ```diff return this.externalAuthenticationService.createAdministratorAndUser(ctx, { strategy: data.strategy, externalIdentifier: data.externalIdentifier, -...

Hi! Thanks for the suggestion. I've not used Relay but as I understand, pagination has to be done in this way for the API to be compatible, is that right?...

Thanks for the link, that's a really good summary. I'll copy the pros/cons of each here for easy reference: --- ### Offset ✔ Pros of offset pagination * You can...

Hi, I don't properly understand the workflow here: When creating a new Payment which only partially covers the order totalWithTax, then the Order should remain in the `ArrangingPayment` state as...

In general I am all for reducing friction to the checkout. In this particular scenario we need to think about the following aspects - whether they are important enough to...

> This way, registered customers are never updated by guests. The trade-off here is that if a customer makes one or more guest orders, and then later registers for an...

Hi, From the info provided on the StackOverflow question, it looks like maybe the database didn't get updated. Did you run a migration after defining the custom field (or have...