the issue is actually that we need auto-discovers to be moved into controllers before that field will practically be used. I can explain more about why, and it doesn't necessarily have to be that way, but I think it's best to just hold off until that's done
Adding new function to get typed AutoComplete props
New control added to the materialization bindings
onIncompatibleSchemaChange
oneOf [string, string, string, string]
Determines how to handle incompatible schema changes for a given binding.
Need to add support for this into the UI. This will probably end up looking like selecting 1 option from a list of 4. We might need to add some extra UI/UX though to explain what these options mean and how they will impact the user.
Add as an advanced section under the time travel section for each binding
Still needs some backend work to be fully implemented
travjenkins
commented
1 month ago
Blocked
the issue is actually that we need auto-discovers to be moved into controllers before that field will practically be used. I can explain more about why, and it doesn't necessarily have to be that way, but I think it's best to just hold off until that's done
Adding new function to get typed AutoComplete props
New control added to the materialization bindings
Need to add support for this into the UI. This will probably end up looking like selecting 1 option from a list of 4. We might need to add some extra UI/UX though to explain what these options mean and how they will impact the user.
Add as an
advanced sectionunder the time travel section for each bindingStill needs some backend work to be fully implemented