If we could change the <EditableNumber /> and <EditablePercentage /> component code so that they respect each other this would be the best outcome. I fear though we will have to use material-ui components within the parent <ValueAndPredictions /> component that contains the <EditableNumber /> and <EditablePercentage /> components to get them to render nicely with each other. If this is the case we should see if there is any way of using the UI library that results in fewer and less leaky abstractions. i.e. it should be possible to use a <EditableNumber /> and <EditablePercentage /> components anywhere without having to embed them within some special html / CSS environment. i.e. these components should come pre-wrapped in that environment already that prevents them from leaking into their parent environment / visa versa.
If we could change the
<EditableNumber />and<EditablePercentage />component code so that they respect each other this would be the best outcome. I fear though we will have to use material-ui components within the parent<ValueAndPredictions />component that contains the<EditableNumber />and<EditablePercentage />components to get them to render nicely with each other. If this is the case we should see if there is any way of using the UI library that results in fewer and less leaky abstractions. i.e. it should be possible to use a<EditableNumber />and<EditablePercentage />components anywhere without having to embed them within some special html / CSS environment. i.e. these components should come pre-wrapped in that environment already that prevents them from leaking into their parent environment / visa versa.