Skip to content

Bug: Relation ignored if same name as Collection #38

@tomh4

Description

@tomh4

I think the latest addition for the ciruclar references introduces a case, where a relationship is ignored while populating if it is named the same as the collection.
E.g:
Collection named "Response" --> strapis plural is responses
The same collection as a field named "responses" which is not the same collection, just a list of values

--> It gets ignored since version 3.0.0

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions