-
-
Notifications
You must be signed in to change notification settings - Fork 32.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Autocomplete] Re-export AutocompleteValue
to make it available from path import
#38638
Conversation
Signed-off-by: Vadim Goy <[email protected]>
Netlify deploy previewhttps://deploy-preview-38638--material-ui.netlify.app/ Bundle size report |
Can you please link the appropriate issue if it exists? Was the component exported before? |
No any issue created |
@mnajdova , can you please provide any update? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@vadimka123 But why do you need the type? How do you use it in your application?
@ZeeshanTamboli , we using this type when building extended AutoComplete with header, footer and other features |
AutocompleteValue
to make it available from path import
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, I am considering this PR. It is available from top level import:
import { AutocompleteValue } from '@mui/material';
So it should be also available from path import:
import { AutocompleteValue } from '@mui/material/Autocomplete';
AutocompleteValue
to make it available from path importAutocompleteValue
to make it available from path import
…m path import (mui#38638) Signed-off-by: Vadim Goy <[email protected]> Co-authored-by: ZeeshanTamboli <[email protected]>
No description provided.