Types are now broken in Grommet, causing prop auto completion to not work.
See original GitHub issueHey guys,
Something is now broken with the types in Grommet. Before, I could write <Box>
and type the first few characters of props like height, pad, width, height etc and my editor would auto complete and suggest available props.
This is now broken.
I’ve verified its not an issue with my editor, by
- Testing other 3rd party components in my app, verifying this issue only effects Grommet.
- Testing Grommet in a completely different IDE, verifying the issue persists.
(version ^2.13.0)
Thank you,
Michael
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (7 by maintainers)
Top Results From Across the Web
Documentation for Grommet - Medium
Didn't change anything in repo except moving prop types in the Button component, and apparently broke several other component's snapshots. Had ...
Read more >React TypeScript type hint auto-completion does not work with ...
It should be because the component's custom types aren't specified. If the types of the expected component's props are specified, then you ...
Read more >Aircraft Electrical Wiring Interconnect System (EWIS ... - FAA
A Complex type of breakout is generally used to route certain wires out of a wire bundle to a terminal strip, module block,...
Read more >Code completion not working in 10.2 | Apple Developer Forums
It gets really annoying now. ... Did you do a Clean Build Folder, forcing some reindex. ... As I noticed Xcode is likely...
Read more >Documentation for Grommet_substance designer_weixin_0010034 ...
How do the Grommet docs currently work? ... Then each prop type is also defined (similar to how you would inside a normal...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Fixed this by manually adding support in Webstorm.
https://stackoverflow.com/a/46871743/1118492
@iMerica are you still experiencing this issue? I was not able to reproduce the issue