[GODRIVER-393] byte stream parsed with extjson and encoded to a document results in extjson looking objects Created: 30/Apr/18 Updated: 03/Oct/19 Resolved: 03/Oct/19 |
|
| Status: | Closed |
| Project: | Go Driver |
| Component/s: | JSON & ExtJSON |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | David Boon | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
A byte stream parsed with extjson and encoded to a document results in a collection entry that looks like:
The relevant code block that produced that entry is:
I would expect the resulting entry to be free of NumberLong. Is there a way to control how the document is stored, why does the document get created with NumberLong? I have created documents programmatically without using the extjson package and those appear fine.
|
| Comments |
| Comment by Esha Bhargava [ 03/Oct/19 ] |
|
davidboon@invisionapp.com The extjson library has been replaced by bson.UnmarshalExtJson. Please update your code and let us know if the problem still exists. |