[Bug]: CollectionTyps with relations

[foodiecompany]

What issue are you experiencing?

The current data lacks complete information about collection Types. It erroneously retains only the attribute count: 1 instead of preserving all attributes related to the collectionItem.

Steps To Reproduce

1. Create CollectionType Events
2. Create CollectionType Table
3. Create relation between Events and Table (Table has many Events)
4. Subscribed to Table:update and Events:update

  connect?.on("table:update", handleTable);
  connect?.on("event:create", handleEvent);
  connect?.on("event:update", handleEvent); 

6. Change some data inside CollectionItem(Events)
7. Missing all attributes inside Table
   

What version of the plugin are you using?

2.0.4

What strapi version are you using?

4.16.2

[ComfortablyCoding]

Thanks for the report! It looks like this is due to webhooks.populateRelations being false in ./config/server.js. Whether this is intentional for this setting I do not know.

For now the workaround is to set webhooks.populateRelations to true. Keep in mind this can have a performance impact.

[foodiecompany]

Thanks for the report! It looks like this is due to webhooks.populateRelations being false in ./config/server.js. Whether this is intentional for this setting I do not know.

For now the workaround is to set webhooks.populateRelations to true. Keep in mind this can have a performance impact.

The current solution is partially effective; however, there are additional issues. When creating a new collectionItem(Event), essential attributes for the related item are missing.

Thanks!

The update process for the collectionItem is functioning correctly.

[ComfortablyCoding]

I cannot reproduce this issue with the provided information. The table relation shows up in the emitted data when an event is updated. Please ensure permissions are correct for whatever role the data is being emitted to.

[ldiellyoungl]

when merging ???

[ComfortablyCoding]

when merging ???

It will be fixed whenever someone has time to research and add a proper fix. The proposed one is not an ideal solution to this issue as it is always populating all fields at first level which has performance ramifications.

This is a small open source project maintained in people's free time their should be no expectation of maintenance and/or fixes applied.

Unfortunately at the moment this project is not maintained by anyone specific, until it is this issue will most likely remain open.

Their is a workaround posted above in #82 (comment)

[ldiellyoungl]

Understood, thanks