Skip to content
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

[test] Use public api in lab #25682

Merged
merged 1 commit into from
Apr 9, 2021

Conversation

vicasas
Copy link
Member

@vicasas vicasas commented Apr 9, 2021

Corresponds to comment #25666 and comment #25666

@mui-pr-bot
Copy link

mui-pr-bot commented Apr 9, 2021

No bundle size changes

Generated by 🚫 dangerJS against 4629139

@vicasas vicasas changed the title [Lab] Using public api to import [lab] Using public api to import Apr 9, 2021
@vicasas
Copy link
Member Author

vicasas commented Apr 9, 2021

Should we do the same in the core?

@mnajdova mnajdova changed the title [lab] Using public api to import [test] Use public api in lab Apr 9, 2021
@mnajdova
Copy link
Member

mnajdova commented Apr 9, 2021

Should we do the same in the core?

Yes, ideally we would use the public API for the test inside the core as well. Although would propose doing it in separate PR.

@vicasas
Copy link
Member Author

vicasas commented Apr 9, 2021

@mnajdova Well, I'll be working on that during the day.

@@ -1,2 +1,5 @@
export { default } from './TabPanel';
export * from './TabPanel';

export { default as tabPanelClasses } from './tabPanelClasses';
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice

@vicasas
Copy link
Member Author

vicasas commented Apr 9, 2021

For the files .d.ts do we use the public api for the [Component]Props?

Example:

- import { PaperProps } from '../Paper';
+ import { PaperProps } from '@material-ui/core/Paper';

and

- import { Theme } from '..'
+ import { Theme } from '@material-ui/core/styles'

?

@oliviertassinari
Copy link
Member

oliviertassinari commented Apr 9, 2021

@vicasas only if the import is coming from another package.

@mnajdova
Copy link
Member

mnajdova commented Apr 9, 2021

Merging this one, so that next PRs can reference the correct imports

@mnajdova mnajdova merged commit c0bdcf0 into mui:next Apr 9, 2021
@vicasas vicasas deleted the bugfix/importing-from-api-public branch April 12, 2021 14:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants