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
Now anything we enter in CLI will cause the whole page refreshed.
This is unnecessary. Failed commands and GET commands should NOT cause refresh.
And if the command won't affect the tree, no need to fetch the tree data as well.
The point is the front-end should make as less API calls as possible.
The text was updated successfully, but these errors were encountered:
Similarly, when user add/update/delete values for list, set, ordered-set, map or string, no need to refresh the tree. You can get the updated-count for the changed key, and set the value to the affected tree node directly.
Now anything we enter in CLI will cause the whole page refreshed.
This is unnecessary. Failed commands and GET commands should NOT cause refresh.
And if the command won't affect the tree, no need to fetch the tree data as well.
The point is the front-end should make as less API calls as possible.
The text was updated successfully, but these errors were encountered: