afterValidate hook? order of hooks (optimistic locking)

[rburgst]

Hi
I am very new to payload and coming from keystonejs.
My question is whether there is a way to add optimistic locking to payload.

The way it would work is that a collection has a version field that will track the version of the users data, if you want to update an entity, then you have to provide the old version. Then during the saving operation, it increments this version to version +1.

The code would look something like this

{
      name: "version",
      label: "Version",
      type: "number",
      required: true,
      defaultValue: 0,
      validate: (value, opts) => {
        console.log(
          "validating version",
          value,
          "data",
          opts.data,
          "op",
          opts.operation,
        );
        if (opts.operation !== "create" && opts.data?.version !== value) {
          return "Optimistic locking error";
        }
      },
      admin: { hidden: false, readOnly: true },
      hooks: {
        beforeChange: [
          (args) => {
            // cannot change the version here as this runs BEFORE the validation.
          },
        ],
        afterChange: [
          (args) => {
            // while this runs after validation , it also runs after saving therefore, any change here is not persisted
            return  args.value + 1;
          },
        ],
      },
    },

So my problem is that the current order of hooks is

• beforeChange
• validate
• save
• afterChange

I would need a hook that allows me to update the value before the save operation but AFTER validation.

[rburgst]

this seems to work better in payload 3