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
We resolved a rather annoying console warning in #838
We should go back and try to fix more of the console errors currently present during testing as well. Here is a sample of a few of the errors
console.error
Warning: Failed prop type: Invalid prop `severity` of value `` supplied to `ForwardRef(Alert)`, expected one of ["error","info","success","warning"].
at Alert (/Users/branden.brown/Documents/SQForm/node_modules/@mui/material/node/Alert/Alert.js:138:44)
at ca (/Users/branden.brown/Documents/SQForm/node_modules/scplus-shared-components/src/components/Snackbar/Snackbar.tsx:12:3)
at Form (/Users/branden.brown/Documents/SQForm/stories/components/SQFormStoryWrapper.tsx:43:3)
at sa (/Users/branden.brown/Documents/SQForm/node_modules/scplus-shared-components/src/contexts/SnackbarContext.tsx:33:28)
at SQFormStoryWrapper (/Users/branden.brown/Documents/SQForm/stories/components/SQFormStoryWrapper.tsx:22:3)
at div
at composedStory
console.error
Warning: Function components cannot be given refs. Attempts to access this ref will fail. Did you mean to use React.forwardRef()?
Check the render method of `MuiInputInput`.
at TextFieldMask (/Users/branden.brown/Documents/SQForm/src/components/fields/SQFormMasked/SQFormMaskedReadOnlyField.tsx:21:3)
at /Users/branden.brown/Documents/SQForm/node_modules/@emotion/react/dist/emotion-element-b63ca7c6.cjs.dev.js:43:23
at div
at /Users/branden.brown/Documents/SQForm/node_modules/@emotion/react/dist/emotion-element-b63ca7c6.cjs.dev.js:43:23
at InputBase (/Users/branden.brown/Documents/SQForm/node_modules/@mui/material/node/InputBase/InputBase.js:224:44)
at Input (/Users/branden.brown/Documents/SQForm/node_modules/@mui/material/node/Input/Input.js:120:44)
at div
at /Users/branden.brown/Documents/SQForm/node_modules/@emotion/react/dist/emotion-element-b63ca7c6.cjs.dev.js:43:23
at FormControl (/Users/branden.brown/Documents/SQForm/node_modules/@mui/material/node/FormControl/FormControl.js:91:44)
at /Users/branden.brown/Documents/SQForm/node_modules/@emotion/react/dist/emotion-element-b63ca7c6.cjs.dev.js:43:23
at TextField (/Users/branden.brown/Documents/SQForm/node_modules/@mui/material/node/TextField/TextField.js:82:44)
at div
at /Users/branden.brown/Documents/SQForm/node_modules/@emotion/react/dist/emotion-element-b63ca7c6.cjs.dev.js:43:23
at Grid (/Users/branden.brown/Documents/SQForm/node_modules/@mui/material/node/Grid/Grid.js:369:49)
at SQFormReadOnlyField (/Users/branden.brown/Documents/SQForm/src/components/fields/SQFormReadOnlyField/SQFormReadOnlyField.tsx:15:3)
at SQFormMaskedReadOnlyField (/Users/branden.brown/Documents/SQForm/src/components/fields/SQFormMasked/SQFormMaskedReadOnlyField.tsx:39:3)
at div
at /Users/branden.brown/Documents/SQForm/node_modules/@emotion/react/dist/emotion-element-b63ca7c6.cjs.dev.js:43:23
at Grid (/Users/branden.brown/Documents/SQForm/node_modules/@mui/material/node/Grid/Grid.js:369:49)
at form
at /Users/branden.brown/Documents/SQForm/node_modules/formik/src/Form.tsx:19:13
at Formik (/Users/branden.brown/Documents/SQForm/node_modules/formik/src/Formik.tsx:992:21)
at SQFormReadOnly (/Users/branden.brown/Documents/SQForm/src/components/SQFormReadOnly/SQFormReadOnly.tsx:34:3)
at div
at /Users/branden.brown/Documents/SQForm/node_modules/@emotion/react/dist/emotion-element-b63ca7c6.cjs.dev.js:43:23
at Paper (/Users/branden.brown/Documents/SQForm/node_modules/@mui/material/node/Paper/Paper.js:68:44)
at /Users/branden.brown/Documents/SQForm/node_modules/@emotion/react/dist/emotion-element-b63ca7c6.cjs.dev.js:43:23
at Card (/Users/branden.brown/Documents/SQForm/node_modules/@mui/material/node/Card/Card.js:42:44)
at composedStory
The text was updated successfully, but these errors were encountered:
We resolved a rather annoying console warning in #838
We should go back and try to fix more of the console errors currently present during testing as well. Here is a sample of a few of the errors
The text was updated successfully, but these errors were encountered: