Add workaround for BigInt field type support as string#1143
Add workaround for BigInt field type support as string#1143MurzNN wants to merge 1 commit intodrupal-graphql:8.x-3.xfrom
Conversation
Codecov Report
@@ Coverage Diff @@
## 8.x-3.x #1143 +/- ##
=============================================
+ Coverage 78.72% 78.73% +0.01%
- Complexity 1139 1141 +2
=============================================
Files 192 192
Lines 3027 3029 +2
=============================================
+ Hits 2383 2385 +2
Misses 644 644
Continue to review full report at Codecov.
|
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## 8.x-3.x #1143 +/- ##
=============================================
+ Coverage 78.72% 78.73% +0.01%
- Complexity 1139 1141 +2
=============================================
Files 192 192
Lines 3027 3029 +2
=============================================
+ Hits 2383 2385 +2
Misses 644 644 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Here is workaround for fix errors with BigInt Drupal field types (Integer with size = big).
Now those fields are represented as 32-bit integer in GraphQL, and throw the error, when value is larger than 32-bit, with inserting
nullin result.This workaround is replacing Integer GraphQL field type to String for those field types, to fix described problem.
Closes #1130