Handle private @Preview annotations gracefully
See original GitHub issueWhen trying to build a project with private Previews, Showkase complains:
The methods annotated with Preview can't be private as Showkase won't be able to access them otherwise
Does it have to be an error? Not all previews are Showkase-worthy, some of them can be used just in ide. Maybe it could be a warning or there could be a gradle flag for this? Wdyt? This should be relatively easy, I could contribute if you decide that it’s a good idea to add it.
Issue Analytics
- State:
- Created a year ago
- Comments:11
Top Results From Across the Web
Annotate a PDF in Preview on Mac - Apple Support
Annotate a PDF in Preview on Mac ; Shapes. Click a shape, then drag it where you want. To resize the shape, use...
Read more >The many superpowers of Apple's Preview app, part 2
Preview 8 introduces five new annotation tools: Star, Polygon, Sketch, Mask and Loupe. Both the Star and Polygon tools are self-explanatory.
Read more >Annotate PDF files using Preview on a Mac
Go to the Tools Menu, choose Annotate, and select the tool of choice. 2. Go to the View Menu, select Show Annotations Toolbar....
Read more >How to Annotate a PDF on Mac
If you want to know how to add annotations to a PDF while on your mac device, we've broken down the process for...
Read more >Exiting gracefully: how to leave a job behind - Nature
Although burning bridges can be tempting, a better approach is to leave goodwill and cheer in your wake.
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 Free
Top 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
Yes, seems like a better idea to warn than to crash. Generally I would agree with you when it comes to the fail fast principle, but here it feels like showkase should be an addition and not hijack the original process. Alternatively maybe a compiler flag or sth to disable this behavior so that we don’t have to use showkase annotations on composables which are not meant for showkase at all.
@iamutkarshtiwari Yeah I’m surprised I had not added that already. I plan to fix this issue this week and I will improve the error logging as well so that you know the source of the error.