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 starting with v6.5.x, we have to define an empty action just to access the config because getLastConfig is undefined.
constconfig=CoreConfig;constreducer=TreeStore(config)// The type INIT_TREE can be whatever you wantconstemptyAction={type: "INIT_TREE", config }conststate=reducer({tree: initTree},emptyAction)
Without this modification, I get this error:
ERROR TypeError: action is undefined
tree_default tree.js:886
And the I can't init the state of my tree.
To Reproduce
Install the v6.5.x and try the example above.
Expected behavior
It should load the state without this empty action.
If it is expected, we have to update the documentation.
The text was updated successfully, but these errors were encountered:
* Optimize render of MuiConjs
* show benchmark in example app
* reuse config extended from memo
* remove internal render optimizations
* use callback, memo
* antd Slider FC
* remove optimizeRenderWithInternals
* .
* fix test
* merge type config to field config @ extend
* fix issue #1056
* fix tests
* fix issue with negative spel #1055
* test spil minus
* chlog
* cache
* fix import of negative number as func arg
* memo
* fix tests
* fix
Describe the bug
A clear and concise description of what the bug is.
With the v.6.4.x and below we can directly load the tree like this:
CoreConfig
is imported from "@react-awesome-query-builder/core"initTree
is just an empty tree build like this:Now starting with v6.5.x, we have to define an empty action just to access the config because
getLastConfig
is undefined.Without this modification, I get this error:
And the I can't init the state of my tree.
To Reproduce
Install the v6.5.x and try the example above.
Expected behavior
It should load the state without this empty action.
If it is expected, we have to update the documentation.
The text was updated successfully, but these errors were encountered: