Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BigInteger on response #1753

Closed
MeskaKeyne opened this issue Mar 11, 2024 · 10 comments · Fixed by #2736
Closed

BigInteger on response #1753

MeskaKeyne opened this issue Mar 11, 2024 · 10 comments · Fixed by #2736

Comments

@MeskaKeyne
Copy link

MeskaKeyne commented Mar 11, 2024

When recieve response , BigInteger is not parse correctly
thanks for help :-)
EDIT: sorry for my mistake on title

@Its-treason
Copy link
Member

Its-treason commented Mar 11, 2024

We recently merged a fix for BigInt that is not yet released: #1710 that might fix your issue. You can either wait for the next Bruno release or clone the repository and start Bruno locally or try a prebuild binary from my fork it includes the BigInt fix.

@MeskaKeyne
Copy link
Author

Many thanks

@Raffine64
Copy link

Raffine64 commented May 15, 2024

json response:
{
"id": 1.0000000000001147e+21
}

still the same issue, tested with Bruno v1.17.0

@MeskaKeyne MeskaKeyne changed the title BigIUnteger on response BigInteger on response May 15, 2024
@azzamsa
Copy link

azzamsa commented Jul 31, 2024

@Its-treason I think it is not included in the latest release. Or Am I missing something?
Bruno still does not get it right.

Bruno:

image

Insomnia

image

@Raffine64
Copy link

@azzamsa, problem still remains, tested with Bruno v1.22.0:

{
"id": 1.0000000000000325e+21,

@Its-treason can you see that it's getting fixed ?

It's very annoying in our day-to-day operations.

@Its-treason
Copy link
Member

@azzamsa, problem still remains, tested with Bruno v1.22.0:

{ "id": 1.0000000000000325e+21,

@Its-treason can you see that it's getting fixed ?

It's very annoying in our day-to-day operations.

Yes, is just looked into it and found a fix. I need to do some testing and will submit a PR later

@helloanoop
Copy link
Contributor

PR #2773 has been merged, This will go out in the v1.27.0 release.

@Raffine64
Copy link

Hello,

I still have the same issue in responses.

tested with Bruno 1.30.1
{
"id": 1.0000000000000104e+21,
...
}

@Its-treason
Copy link
Member

Its-treason commented Sep 23, 2024

Hello,

I still have the same issue in responses.

tested with Bruno 1.30.1 { "id": 1.0000000000000104e+21, ... }

Yeah, the PR I created with a fix get reverted. The new solution is to call req.disableParsingResponseJson() in the pre-request script.

@Raffine64
Copy link

thanks for your answer @Its-treason.

but the problem is that now my responses are not pretty printed (not formatted).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants