Error adding a new item to repeatable component

[chadwithuhc]

Bug report

Describe the bug

I am trying to add a new item to a repeatable component field through an API PUT /api/[api-name]/:id. I expected to be able to push a new item on the array without an ID and it will be created, but I receive an error instead. I am not sure if this is a bug or my misunderstanding of the API.

Steps to reproduce the behavior

Example of Lists Content Type

1. Inside my beforeUpdate() lifecycle hook for my Lists API,
2. I try to add a new item to my existing items array by using:

event.params.data.items.push({
  title: "Washcloths",
  checked: true
})

3. I can see it is properly added to the data

// event.params.data
{
  title: 'Craigslist',
  items: [ { title: 'Washcloths', checked: true } ],
  updatedAt: 2021-12-22T00:21:36.488Z
}

4. Then I get the error error: Invalid id, expected a string or integer, got [object Object] once it is run

Error: Invalid id, expected a string or integer, got [object Object]
    at node_modules/@strapi/database/lib/entity-manager.js:25:15

Expected behavior

I would expect it to create a new item for me.

System

• Node.js version: v16.13.0
• NPM version: 8.1.0
• Strapi version: 4.0.0
• Database: sqlite3
• Operating system: Mac OS Monterrey

[iicdii]

I did console.log in source code and I found the difference between manual data and internal data.

[
  {
    id: 3,
    __pivot: { order: 1, field: 'items', component_type: 'default.items' }
  }, // from internal entity-manager
  { title: 'Washcloths', checked: true } // from beforeUpdate lifecycle
]

I think the data from beforeUpdate lifecycle should also be converted too in internal code. (like automatically adding id, order etc..)

You can use different approach like below though - overriding your core service

// src/api/list/services/list.js

module.exports = createCoreService('api::list.list', ({ strapi }) =>  ({
  async update(entityId, params) {
    params.data.items = (params.data.items || []).concat({
      title: "Washcloths",
      checked: true
    });
    const result = await super.update(entityId, params);

    return result;
  }
}));

[chadwithuhc]

That solves my problem for now, thanks @iicdii !

[derrickmehaffy]

This issue has been mentioned on Strapi Community Forum. There might be relevant details there:

https://forum.strapi.io/t/lifecycle-and-components-inside-collections-type/14003/2

[osmanorhan]

This issue still persists.

[LouisLec]

Well, this is actually preventing me from getting to v4... Is it planned to include component data in lifecycles ?

And what about lifecycles on components (just thinkin'...)

[DeploymentService]

is there a way to convert the data from beforeUpdate format into an internal code and give it an id ? @iicdii

[iicdii]

@DeploymentService I don' think that's possible. and also dangerous - you don't know when internal code'd be changed in the future. Currently it's the best way to override the core service like example in comments.

[WardenCommander]

I think lifecycles on components would help alot of people and open alot of new possibilities

[derrickmehaffy]

This is being discussed internally, is everyone here trying to use components inside of lifecycles?

We are looking at this issue more broadly than just as a bug.