[Autocomplete] types break when having multiple default values
See original GitHub issueDuplicates
- I have searched the existing issues
Latest version
- I have tested the latest version
Steps to reproduce 🕹
Link to live example: https://codesandbox.io/s/wrong-types-in-autocomplete-with-multiple-default-values-b5qtpu
Steps:
- Use an Autocomplete component with the following props
a.
multiple
b.options
passing an array of objects c.defaultValue
passing an array of objects of the same type as the options - See type errors.
Current behavior 😯
Functionality works as expected.
Type error thrown: Type 'T[]' is not assignable to type 'readonly T[][]'.
Expected behavior 🤔
No type error should be thrown, since the passed values are correct. It should not expect an array of arrays.
Context 🔦
The goal is to have an array of default values that has the same type as the array of options.
Your environment 🌎
npx @mui/envinfo
System:
OS: macOS 12.0.1
Binaries:
Node: 16.10.0 - ~/.nvm/versions/node/v16.10.0/bin/node
Yarn: 1.22.19 - /opt/homebrew/bin/yarn
npm: 7.24.0 - ~/.nvm/versions/node/v16.10.0/bin/npm
Browsers:
Chrome: 107.0.5304.110
Edge: Not Found
Firefox: Not Found
Safari: 15.1
npmPackages:
@emotion/react: ^11.10.5 => 11.10.5
@emotion/styled: ^11.10.5 => 11.10.5
@mui/base: 5.0.0-alpha.105
@mui/core-downloads-tracker: 5.10.13
@mui/material: ^5.10.13 => 5.10.13
@mui/private-theming: 5.10.9
@mui/styled-engine: 5.10.8
@mui/system: 5.10.13
@mui/types: 7.2.0
@mui/utils: 5.10.9
@types/react: ^18.0.25 => 18.0.25
react: ^18.2.0 => 18.2.0
react-dom: ^18.2.0 => 18.2.0
typescript: ^4.8.4 => 4.8.4
tsconfig.json
{
"compilerOptions": {
"target": "es5",
"lib": [
"dom",
"dom.iterable",
"esnext"
],
"allowJs": true,
"skipLibCheck": true,
"esModuleInterop": true,
"allowSyntheticDefaultImports": true,
"strict": true,
"forceConsistentCasingInFileNames": true,
"noFallthroughCasesInSwitch": true,
"module": "esnext",
"moduleResolution": "node",
"resolveJsonModule": true,
"isolatedModules": true,
"noEmit": true,
"jsx": "react-jsx"
},
"include": [
"src"
]
}
Issue Analytics
- State:
- Created 10 months ago
- Reactions:1
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Material UI Autocomplete, multiple default values
I have a working material ui auto component that has the following code: <Autocomplete multiple options ...
Read more >Autocomplete multiple default value #19881 - mui/material-ui
The autocomplete show the twos items but the list is not selected and i have the twos first item in double. I try...
Read more >Fatal errors during or after adding default values for ... - Drupal
Through testing, it appears that submitting a custom content type with no entry in the default taxonomy term field (using the autocomplete ......
Read more >HTML attribute: autocomplete - MDN Web Docs
The HTML autocomplete attribute lets web developers specify what if any permission the user agent has to provide automated assistance in ...
Read more >AutoCompleteTextView - Android Developers
Hint indicating that this view can be autofilled with a username. int, AUTOFILL_TYPE_DATE. Autofill type for a field that contains a date, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi @ZeeshanTamboli and @samkevin1, can I make a pr for this issue? Seems like I find out how to fix it.
@ZeeshanTamboli can I look into this and try to find a solution?