Field names can clash with API code, causing errors when creating records #791
Labels
issue: bug
Issue reporting a bug
severity: low
If the issue only affects a very niche base of users and an easily implemented workaround can solve
Milestone
Node.js version:
9.8.0
npm version:
5.7.1
Strapi version:
3.0.0-alpha.11.1
Operating system:
OSX El Capitan
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
If you make a field with a name that clashes with a Model/orm method or property (might be something else, this is a guess), you will be unable to create records using the content type UI.
In my case, I was trying to use a field named "set" on one of my content types. I could not create any more records. Updates still worked fine.
If the current behavior is a bug, please provide the steps to reproduce the problem
The server console reports:
error: undefined
The http response reports:
What is the expected behavior?
Either field names like this are prevented from clashing with API code, or are not allowed to be entered in the content type manager at all.
The text was updated successfully, but these errors were encountered: