Replies: 2 comments 1 reply
-
@gorghoa yeah that is because you've run into javascript's integer limit. So if you need really big ints, you should convert them to strings before they get sent to the browser. Hope this helps! |
Beta Was this translation helpful? Give feedback.
1 reply
-
Same problem here! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
First of all, thank you for livewire, it really makes our life easier ❤️ !
We recently were bitten by a "Livewire encountered corrupt data when trying to hydrate the … component" exception when using a component (livewire 2.10.4).
We eventually found out that one of our property was a very large integer, larger than the javascript
Number.MAX_SAFE_INTEGER
(mdn) which can be lower than the php max limitPHP_INT_MAX
(php doc).The value of the js integer was not the same as the php one => hence corruption.
herafter, a crash test:
Beta Was this translation helpful? Give feedback.
All reactions