fix (crud): update idempotent methods to match argument's order

[lolio-dev]

📚 Description

Changing the arguments order for the fetchOrCreateMany and updateOrCreateMany in the examples to reflect reality.

[lolio-dev]

@RomainLanz poke

[RomainLanz]

Hey @lolio-dev! 👋🏻

I am not sure you are right. Looking at the source code, the current signature is correct.

/**
 * Find existing rows or create missing one's. One database call per insert
 * is invoked, so that each insert goes through the lifecycle of model
 * hooks.
 */
static fetchOrCreateMany(uniqueKeys: any, payload: any, options?: ModelAssignOptions): Promise<any[]>;

/**
 * Update existing rows or create missing one's. One database call per insert
 * is invoked, so that each insert and update goes through the lifecycle
 * of model hooks.
 */
static updateOrCreateMany(uniqueKeys: any, payload: any, options?: ModelAssignOptions): Promise<any>;

[lolio-dev]

Hi @RomainLanz, when I look in the source code in local, I don't have at all the same code as you but I have this:

    fetchOrCreateMany(payload: Partial<ModelAttributes<InstanceType<RelatedModel>>>[], predicate?: keyof ModelAttributes<InstanceType<RelatedModel>> | (keyof ModelAttributes<InstanceType<RelatedModel>>)[], options?: ModelAssignOptions): Promise<InstanceType<RelatedModel>[]>;
    /**
     * Update or create rows. Providers a great API to sync rows
     */
    updateOrCreateMany(payload: Partial<ModelAttributes<InstanceType<RelatedModel>>>[], predicate?: keyof ModelAttributes<InstanceType<RelatedModel>> | (keyof ModelAttributes<InstanceType<RelatedModel>>)[], options?: ModelAssignOptions): Promise<InstanceType<RelatedModel>[]>;

I am with the last version of lucid (20.5.1)