Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Falling back to float when serializing of JavaScript 'number'
See original GitHub issueI have code that calls EvaluateExpressionAsync in order to return a value, the value can be an object or primitive so I don’t specify the ‘T’, which defaults to “object”. I do this so that I can later choose how to represent the value as string.
The issue I have is that ValueFromRemoteObject defaults to a floating point number if the ‘T’ isn’t int32/64.
await new BrowserFetcher().DownloadAsync(BrowserFetcher.DefaultRevision);
var browser = await new Launcher().LaunchAsync(new LaunchOptions
{
Headless = true,
});
var page = await browser.NewPageAsync();
var javascript = "<html><body><script type=\"text/javascript\">var obj = { \"int64\": 11111111111111 };</script></body></html>";
await page.SetContentAsync(javascript);
var result = await page.EvaluateExpressionAsync("obj.int64"); // result is System.Single
var str = Convert.ToString(result); // str is 1.111111E+13
browser.Dispose();
There needs to be some kind of intelligent numeric type detection such as the ParseReadNumber used by Newtonsoft Json.Net so that my result is an integer.
Issue Analytics
- State:
- Created 5 years ago
- Comments:12 (12 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
If I get time later this evening I’ll have a go at forking and cutting back some of the dynamic to make things like this easier.
and we should really deprecate/remove the
dynamicoverload, it’s a source of weird bugs