-
Notifications
You must be signed in to change notification settings - Fork 2
feature(jv-input-controls): Cascading Input Controls #96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
add reducer to manage the state of the input controls
… response to the reducer
…ach option on the selects
…and put everything inside events.change because the updates happens on the state now.
… has slaveDependencies. The work is not done yet, having issues with the reducer and the local state of each component.
…xt API. it also includes the work for avoiding duplication of the request for the same chain of input controls
missing: to make all slave dependencies to behave the same way as the immediate slave dependency
…s to the state instead of BasePanel
…on for single input controls so that the user can know if the value is okay or not
…change for the cascading input controls
…ntrol is being updated
… logic for updating the options for single and multi select input control
…change method multiple times for single and multi select input control
…and Multi Select input controls
…use the cascading feature was added to Single and Multi Select input controls, hence the other Input Controls had to be updated. - This commit adds the changes for Boolean, and SingleValueText - Changes on MultiSelect, and SingleSelect Input control are for removing params that need to be put on a more general interface.
…ueNumber Input Control has been added.
…ted in order to store the values in the store.
…een updated in order to store the values in the store.
…ted in order to store the values in the store.
…he store (cascading feature)
… (cascading feature). The main feature of the cascading feature for this IC is already tested on the useChangeCallback test
…es for the context/dispatch (cascading feature).
…new changes for the context/dispatch (cascading feature).
…changes for the context/dispatch (cascading feature).
…nges for the context/dispatch (cascading feature).
…ges for the context/dispatch (cascading feature).
…or the context/dispatch (cascading feature).
… cascading feature starts
… the values from the server for cascading feature
…urn the same options for different scenarios
…rendering This will fix the tests and the first rendering (no error in the browser console)
…or rendering the input controls
|
I propose to merge |
… publicPath, and server as parameters
both properties have been merged. even |
This PR adds the feature for having cascading input controls.

Additionally, the jv-tools package accepts an object when using the useVisualize custom hook to provide the server and the context path:
this will add the server property to the vObject:
