You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 14, 2025. It is now read-only.
If we do not explicitly import RippledComponentProps the resulting typefile attempts a relative import at the bottom (import("../ripple").RippledComponentProps).
If we do explicitly import RippledComponentProps (and use/export it as required to avoid lint errors) the resulting typefile is able to directly use the imported type (RippledComponentProps).
This appears to be an issue in typescript resolution/expansion itself. The import at the top is left alone, but the generated one at the bottom will default to a relative import.
arichiv
changed the title
[BLOCKED] fix(typescript) remove extraneous imports
fix(typescript) remove extraneous imports
Jul 8, 2019
Thanks for doing some more investigation. It sounds like this is a TypeScript bug then? We can leave this open until there is a fix and we update to that version. How does that sound?
#953 adds a bunch of imports to fix an error in typescript type expansion. They should be removed at some point.
Each one looks like:
Each one should be reduced to:
The text was updated successfully, but these errors were encountered: