-
Notifications
You must be signed in to change notification settings - Fork 8
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
Publish to DefinitelyTyped as @types/rmwc #5
Comments
We're discussing whether to publish to @kctang: Feel free to comment there too! |
This project as is should not be published to DefinitelyTyped. I suggest to mimic the flow types much closer, so that edits can be made by anyone. For example declare module 'rmwc/Base' {
export { simpleTag, SimpleTagProps } from 'rmwc/Base/simpleTag'
export { withRipple, WithRippleProps } from 'rmwc/Base/withRipple'
export { withTheme, WithThemeProps } from 'rmwc/Base/withTheme'
export { withMDC } from 'rmwc/Base/withMDC'
export { withMDCToggle } from 'rmwc/Base/withMDCToggle'
export { noop } from 'rmwc/Base/noop'
} Which is exactly the same exports the actual javascript library has (in flow + js). |
I agree with @SleeplessByte that it should not be published as is, but for different reasons.
import {
Toolbar
} from "rmwc"; This has the unfortunate side effect of importing all of the import {
Toolbar
} from "rmwc/Toolbar"; which is in accordance with the recommendations of the
|
If you apply what I said you solve both issues you describe; and I completely agree with those two points. I think James (rmwc) is still looking to compile definitions automagically, which would be great. |
Thank you @mutsys for your PR. It's now been merged. |
Thanks for providing
rmwc-typed
. Can we publish it to DefinitelyTyped as@types/rmwc
?The text was updated successfully, but these errors were encountered: