| Summary: | EGL record wizard from the JSON file results in the overflow of int type | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | pf yu <pfyu> |
| Component: | EDT | Assignee: | Zhi Zhu <zhuzhi> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | jinfahua |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
The defect is not found by FVT and have little impact on EDT, so delay it for future fix discuss with Thomas, he agrees to defer this |
Build Identifier: 0.7.0 all in one If a JSON file contains string like this: { "people": [ { "id": 1234567890123, "lastName":"McLaughlin", "email": "aaaa" } ]} When new an EGL record using the json string above, the type of the id will be "int", which is incorrect because the value is overflow: Record fdsafdsa people People[]; end Record People id int; lastName string; email string; end We need a mechanism to automatically recognize the type of field in the json string. This problem exists in both RBD and EDT. Reproducible: Always Steps to Reproduce: If a JSON file contains string like this: { "people": [ { "id": 1234567890123, "lastName":"McLaughlin", "email": "aaaa" } ]} When new an EGL record using the json string above, the type of the id will be "int", which is incorrect because the value is overflow: Record fdsafdsa people People[]; end Record People id int; lastName string; email string; end We need a mechanism to automatically recognize the type of field in the json string. This problem exists in both RBD and EDT.