Access to payload object on plugin initialization

khakimvinh2 years ago

1 1

• Selected Answer
  

  denolfe

  2 years ago

  Hey @khakimvinh , this is a great question. All config and plugin initialization is done before accessing the backend.

  If you need your plugin to perform some sort of action, your plugin could utilize the onInit function of the config, which gives it access to the payload local API. Here is an example:

    onInit: async (payload) => {
      await payload.create({
        collection: 'my-collection',
        data: {
          // Set field values here
        },
      });
    },

  Worth noting that if you populate this function inside of your plugin, any other onInit usage will likely be wiped out.

  Because this is a function and not a property that can be spread - what I'd recommend is having your plugin export an additional function that can be put into the main config's onInit. This would mitigate the above issue. Give that a go and let me know if you run into any issues 👍

  1 reply
• 

  khakimvinh2 years ago

  Thank you very much @denolfe
  I somehow missed the onInit in the doc...