Skip to content
This repository has been archived by the owner on Sep 2, 2022. It is now read-only.

Problems with migrating float fields #574

Closed
marktani opened this issue Sep 20, 2017 · 1 comment
Closed

Problems with migrating float fields #574

marktani opened this issue Sep 20, 2017 · 1 comment
Assignees

Comments

@marktani
Copy link
Contributor

What is the current behavior?

Making different changes from or to float fields results into internal server error.

Please share the relevant part of your project (GraphQL schema, functions, permissions, ...) for easier reproduction

The following are all using updateField in the System API:

  • Updating a required String field to a required Float field doesn't work: eu-west-1:system:cj7tdbshy0u4h01114aplglfe
  • Updating the default value to null from 1 on a required Float field doesn't work: eu-west-1:system:cj7tdfd260uip01093q7hyk3h
  • In general, it looks like passing defaultValue: null to the updateField mutation results in internal server error.

What is the expected behavior?

The respective mutations work.

@marktani
Copy link
Contributor Author

This works now 💯

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

No branches or pull requests

2 participants