Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Wildcard support in acceptClasses / rejectClasses
See original GitHub issueThe docs for acceptClasses and rejectClasses mention
May not include a glob wildcard (*).
Is this something you’d consider supporting in the future, or are there fundamental reasons why it isn’t supported?
My use-case is scanning large jars for classes annotated with a particular annotation, and I’m seeing some OOMs. The annotated classes aren’t necessarily in the same package, but they all follow a naming convention and have the same suffix, so it would be useful to be able to filter for names matching that suffix with something like acceptClasses("*Suffix.class").
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yes, that matches the change I tried, thanks!
Thanks for your response, and for the bug report – released as 4.8.111!