Project:
| View Revisions: Issue #34077 | [ Back to Issue ] | ||
| Summary | 0034077: Unnecessary set of json property with wrong value when saving cusotmer(address) | ||
| Revision | 2016-09-24 14:14 by mtaal | ||
| Steps To Reproduce | Put breakpoints in the changed locations and check what is being set in the object's json property | ||
| Revision | 2016-09-24 14:14 by mtaal | ||
| Description | There are several places in the customer address code where the json property is set in the wrong way and unnecessarily as it was already set correctly. |
||
| Revision | 2016-09-24 13:56 by mtaal | ||
| Steps To Reproduce | Put breakpoints in the changed locations and check what is being set in the object | ||
| Revision | 2016-09-24 13:56 by mtaal | ||
| Description | In many places in the code we see this pattern: bpLocToSave.set('json', JSON.stringify(customerAddr.serializeToJSON())); bpToSave.set('json', JSON.stringify(customer.serializeToJSON())); However there are some places in the code where don't do this yet: bpToSave.set('json', customer.serializeToJSON()); this seems to be wrong as we then set an object in the json property while the rest of our code treats it as a string. |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |