Closed
Description
I have a couple of cases where json view is rendering data not in the source file.
here is example 1 (_versions.json)
{
"asset_id": "336541846568177664",
"versions": [
[336541846568177665, "http://aarons-mbp-2011.local/api/assets/336541846568177664/336541846568177665"],
[336541849961369600, "http://aarons-mbp-2011.local/api/assets/336541846568177664/336541849961369600"]
]
}When this renders the integer in the fist item in the list is wrong, it's 336541846568177660 see https://dl.dropbox.com/u/11493551/_versions.jpg
This is the item example:
{
"files": {
"vulture.jpg": {
"name": "vulture.jpg",
"exif": {},
"tags": [
"source"
]
}
},
"updated": {
"timestamp": "2012-07-17T03:17:08Z",
"user": "aaron@foo.com"
},
"tags": [
""
],
"taxonomy": {},
"related": {},
"id": 336541846568177664,
"title": "vulture",
"created": {
"timestamp": "2012-07-17T03:17:08Z",
"user": "aaron@foo.com"
},
"version": 336541846568177665,
"storage_app": "reflib",
"storage_bucket": "336541846568177666"
}It renders both the id and version fields as having the value 336541846568177660 see https://dl.dropbox.com/u/11493551/item.jpg
The issue seems to be with handling long integers (the ones that work are strings).
Any thoughts ?
Metadata
Metadata
Assignees
Labels
No labels