-
-
Notifications
You must be signed in to change notification settings - Fork 31.6k
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
Re exports in @material-ui/core/styles from @material-ui/styles #16147
Comments
If this doesn't have any impact other than stylistic I'd rather not change it. |
In some of the docs inline exports have been used maybe we can change the packages to inline exports for consistency. |
So for consistency purpose maybe it is a good idea to change these re exports to an inline re exports |
I’m not sure if this is that important, I’m not against the change but it’s definitely low priority and is only stylistic. |
If it's only stylistic than I'd rather avoid it. |
But why are we re exporting from |
This is just there for convenience.
I don't understand that statement. Those are the exact same paths you mentioned. |
In the package wherever we have |
Since ThemeProvider in |
It is there for convenience. You can follow the git blame to find more context about this change. |
@aditya1906 Thanks for the proposal, I agree with Sebastian, it won't make a difference. |
👍 |
@oliviertassinari if you don't mind can you review #16137? |
@aditya1906 I'm aware of this pull request. Asking won't change my priorities. Soon or later I will come to it. No rush :) |
👍 No problem |
In
@material-ui/core/styles
we export as default from@material-ui/styles
For example:import { ThemeProvider } from '@material-ui/styles';
export default ThemeProvider;
Can we re export it as default like this?
export {ThemeProvider as default} from '@material-ui/styles'
If you are happy with this idea. I'll create a Pull Request with these changes.
The text was updated successfully, but these errors were encountered: