Currently, we have a MUI Autocomplete component being used for our SetAclPermissionsModal. However, the current modal trigger warnings by MUI by passing the incorrect props/attributes/etc.
After a big of digging, I believe I have isolated the problem. I'll post the potential solution after saying how to reproduce.
Which is why the solution for this should be to remove the incompatible props from Autocomplete and move the values used in there with the TextField inside the renderInput prop.
Additionally, the webId comes out undefined, which means the webId is likely not being passed through our existing React Context for SignedInUserContext.
Describe the bug:
Currently, we have a MUI Autocomplete component being used for our
SetAclPermissionsModal
. However, the current modal trigger warnings by MUI by passing the incorrect props/attributes/etc.After a big of digging, I believe I have isolated the problem. I'll post the potential solution after saying how to reproduce.
To Reproduce:
Steps to reproduce the behavior:
Possible Fix:
The problem likely lies with props like
helperText
being used in Autocomplete. However, these props are not part of the component (https://mui.com/material-ui/api/autocomplete/). However, they are props forTextField
(https://mui.com/material-ui/api/text-field/).Which is why the solution for this should be to remove the incompatible props from Autocomplete and move the values used in there with the
TextField
inside therenderInput
prop.Additionally, the
webId
comes out undefined, which means the webId is likely not being passed through our existing React Context forSignedInUserContext
.