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
For complex custom column content, maybe need to declare some variables (which can be reactive variables) in the "customrender" function block to store the state of the rendering component. For example, there is an "approval button" in the "operation" column, and the "loading" variable is declared in the scope of the "customrender" function block. When clicked, initiate a remote request and set the "loading" status. The current situation is that when the mouse moves, the "customrender" function will be triggered again, resulting in resetting the variable state. A switch is required to trigger the "customrender" function only once during the initial rendering.
What does the proposed API look like?
Table's prop "customRenderOnce"
The text was updated successfully, but these errors were encountered:
What problem does this feature solve?
对于复杂的自定义列内容,可能需要在“customRender”函数块声明一些变量(可以是响应式变量)来储存渲染组件的状态。比如“操作”列有一个“审批按钮”,“loading”变量声明在“customRender”函数块作用域。点击时发起远程请求,并且设置“loading”状态。现在的情况是鼠标移出行时就会再次触发“customRender”函数,导致重置变量状态。需要有一个开关使“customRender”函数只在初始渲染时触发一次。
For complex custom column content, maybe need to declare some variables (which can be reactive variables) in the "customrender" function block to store the state of the rendering component. For example, there is an "approval button" in the "operation" column, and the "loading" variable is declared in the scope of the "customrender" function block. When clicked, initiate a remote request and set the "loading" status. The current situation is that when the mouse moves, the "customrender" function will be triggered again, resulting in resetting the variable state. A switch is required to trigger the "customrender" function only once during the initial rendering.
What does the proposed API look like?
Table's prop "customRenderOnce"
The text was updated successfully, but these errors were encountered: