{"action":"created","issue":{"url":"https://api.github.com/repos/JamesNK/Newtonsoft.Json/issues/666","repository_url":"https://api.github.com/repos/JamesNK/Newtonsoft.Json","labels_url":"https://api.github.com/repos/JamesNK/Newtonsoft.Json/issues/666/labels{/name}","comments_url":"https://api.github.com/repos/JamesNK/Newtonsoft.Json/issues/666/comments","events_url":"https://api.github.com/repos/JamesNK/Newtonsoft.Json/issues/666/events","html_url":"https://github.com/JamesNK/Newtonsoft.Json/issues/666","id":108267188,"number":666,"title":"The precision of double serialization","user":{"login":"bargitta","id":5974987,"avatar_url":"https://avatars.githubusercontent.com/u/5974987?v=3","gravatar_id":"","url":"https://api.github.com/users/bargitta","html_url":"https://github.com/bargitta","followers_url":"https://api.github.com/users/bargitta/followers","following_url":"https://api.github.com/users/bargitta/following{/other_user}","gists_url":"https://api.github.com/users/bargitta/gists{/gist_id}","starred_url":"https://api.github.com/users/bargitta/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bargitta/subscriptions","organizations_url":"https://api.github.com/users/bargitta/orgs","repos_url":"https://api.github.com/users/bargitta/repos","events_url":"https://api.github.com/users/bargitta/events{/privacy}","received_events_url":"https://api.github.com/users/bargitta/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2015-09-25T05:37:53Z","updated_at":"2016-04-20T01:04:47Z","closed_at":"2015-09-30T02:40:30Z","body":"I use this package with Microsoft Web API2. When serialize a C# double (64bit) to json, and convert the json back to javascript double (64bit), I find there will be precision loss. Anything I can configure there?"},"comment":{"url":"https://api.github.com/repos/JamesNK/Newtonsoft.Json/issues/comments/212190352","html_url":"https://github.com/JamesNK/Newtonsoft.Json/issues/666#issuecomment-212190352","issue_url":"https://api.github.com/repos/JamesNK/Newtonsoft.Json/issues/666","id":212190352,"user":{"login":"challenh","id":6153066,"avatar_url":"https://avatars.githubusercontent.com/u/6153066?v=3","gravatar_id":"","url":"https://api.github.com/users/challenh","html_url":"https://github.com/challenh","followers_url":"https://api.github.com/users/challenh/followers","following_url":"https://api.github.com/users/challenh/following{/other_user}","gists_url":"https://api.github.com/users/challenh/gists{/gist_id}","starred_url":"https://api.github.com/users/challenh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/challenh/subscriptions","organizations_url":"https://api.github.com/users/challenh/orgs","repos_url":"https://api.github.com/users/challenh/repos","events_url":"https://api.github.com/users/challenh/events{/privacy}","received_events_url":"https://api.github.com/users/challenh/received_events","type":"User","site_admin":false},"created_at":"2016-04-20T01:04:47Z","updated_at":"2016-04-20T01:04:47Z","body":"@JamesNK  thank you. In some other scenarios where user is unable to predict the numeric value & call ReadAsString(), I think the important thing is to read the accurate value out (no matter as decimal or as double, and with as much precision as possible) , then let user do further processing. so do you think this feature request is valid? \r\n\r\nBased on that, I have reverted the previous change, then add Json.FloatParseHandling.Auto for trying decimal precision first and fallback to double if needed. it is the same PR: #884 "}}