You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
maybe i am not getting it, why this is the case, however isn't it little bit strange to send back initialData (it is fired on document save)?
I don't know how it is in react or vue, but it seems to be bit too cumbersome to compare if it is initData or mergeData and there isn't any message in callback as what data this is (there is some in the window event, though).
If the return would be null, it would be comparable at least - but initialData just seem strange choice.
I would be greatful for any insight into this - or how would one go about easily discerning if this is newData or initData.
okey, my bad - i guess i can just compare the two (i just have to not spead the object - naturally). however still it seems, that could be some assertion as what event just happen: live edit or document save
Hi,
maybe i am not getting it, why this is the case, however isn't it little bit strange to send back initialData (it is fired on document save)?
I don't know how it is in react or vue, but it seems to be bit too cumbersome to compare if it is initData or mergeData and there isn't any message in callback as what data this is (there is some in the window event, though).
If the return would be null, it would be comparable at least - but initialData just seem strange choice.
I would be greatful for any insight into this - or how would one go about easily discerning if this is newData or initData.
Thanks
payload/packages/live-preview/src/handleMessage.ts
Line 62 in 00cc10c
The text was updated successfully, but these errors were encountered: