[SOLVED] Field name changes from "content" to "contentEntity" in API dto

[Simon]

I have…

• [ x] Read the following guideline: https://docs.squidex.io/01-getting-started/installation/troubleshooting-and-support. I understand that my support request might get deleted if I do not follow the guideline.

I’m submitting a…

• [x] Regression (a behavior that stopped working in a new release)
• [ ] Bug report
• [ ] Performance issue
• [ ] Documentation issue or request

Current behavior

After updating to Squidex 5.6, from 5.5, field names within the api data dtos have changed from content to contentEntity. Therefore queries which are using the content field do not work anymore.

Expected behavior

The field name within the API is the same as it is in the schema.

Minimal reproduction of the problem

Create a schema, add a field with the name content. Look at the generated API names wich is contentEntity instead of content.

Environment

• [x] Self hosted with docker
• [ ] Self hosted with IIS
• [ ] Self hosted with other version
• [ ] Cloud version

Version: 5.6

Browser:

• [x] Chrome (desktop)
• [ ] Chrome (Android)
• [ ] Chrome (iOS)
• [ ] Firefox
• [ ] Safari (desktop)
• [ ] Safari (iOS)
• [ ] IE
• [ ] Edge

Others:

[Sebastian]

Hi, I guess you are talking about GraphQL?

I have made a few improvements there and one of them was to avoid naming conflicts. Content is a reserved keyword for types, but I guess I also apply this rule to field names.

I will have a look.

[Simon]

Hi,

thanks for the quick reply. Yes, I’m talking about GraphQL, sorry.

[ben]

I was just about to raise the same issue. We have a field called content and have just upgraded from 5.4.0 to 5.6.0. Also experience issue when using GraphQL

[Sebastian]

It is fixed: https://build.squidex.io/Squidex/squidex/ … it will be dev-5715