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
While using yorkie.Tree, an error occurs only in the dashboard, not in the app, when trying to view document. The error message is left and right are not in the same list.
Update the API key in the code and open the browser.
(You can get the API key of the project on Dashboard.
Before clicking the button, the document displays correctly on the dashboard.
When clicking the button, the tree.styleByPath is executed, which results in an error on the dashboard.
Probable Cause:
The issue occurs when retrieving documents in the dashboard using the admin API GetDocument. During the handling of the GetDocument request on the server, the document is built using BuildDocumentForServerSeq(go). However, in the app, the document is built using js-sdk. So, there seems to be a difference in behavior between Go and JS-SDK, leading to errors in the dashboard(Go) but not in the app(JS-SDK).
Environment:
Yorkie JS SDK version: v0.4.4
The text was updated successfully, but these errors were encountered:
Description:
While using
yorkie.Tree
, an error occurs only in the dashboard, not in the app, when trying to view document. The error message isleft and right are not in the same list.
tree-error.mov
How to reproduce:
API key
in the code and open the browser.(You can get the
API key
of the project on Dashboard.tree.styleByPath
is executed, which results in an error on the dashboard.Probable Cause:
The issue occurs when retrieving documents in the dashboard using the admin API
GetDocument
. During the handling of the GetDocument request on the server, the document is built usingBuildDocumentForServerSeq
(go). However, in the app, the document is built using js-sdk. So, there seems to be a difference in behavior between Go and JS-SDK, leading to errors in the dashboard(Go) but not in the app(JS-SDK).Environment:
v0.4.4
The text was updated successfully, but these errors were encountered: