Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

naming a field "id" causes data loss #4333

Closed
rpalmite opened this issue Oct 23, 2019 · 1 comment
Closed

naming a field "id" causes data loss #4333

rpalmite opened this issue Oct 23, 2019 · 1 comment

Comments

@rpalmite
Copy link

Describe the bug
A clear and concise description of what the bug is.

Steps to reproduce the behavior

  1. Create a content type
  2. Name a string field "id"
  3. Create a couple other fields (say description etc)
  4. Create a couple instances of the above type (including typing in ids)
  5. View the new record and notice the id field is an auto-generated guid and not the id you entered into step 4

Expected behavior
It should keep the entered id field values

Screenshots

System

  • Node.js version:
  • NPM version:
  • Strapi version: Strapi v3.0.0-alpha.26.2
  • Database:
  • Operating system:
@derrickmehaffy
Copy link
Member

The ID name is. Reserved word, @soupette you want to add that to the list? I know the beta doesn't allow it.

@rpalmite strapi alpha is no longer supported, for that reason I am closing this as it won't be fixed on alpha.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants