Javadoc doesn't seem to like having e.g. as it thinks the sentence ends there which is usually incorrect and results in broken descriptions. Replacing the breakable space with a nonbreakable one works around it.
Comment From: snicoll
@deejay1 thanks for the proposal but I am not a fan of the change. Rather, we could update the phrasing to avoid the use of "e.g." or make the first sentence shorter (that's definitely the case for one of them). Do you want to amend your proposal?
Comment From: deejay1
@snicoll yeah, I'm not that much of a fan either, I'll see if I can come up with something better
Comment From: sbrannen
I agree with @snicoll. Let's not introduce .
I've heard from documentation experts that Latin abbreviations like "e.g." should be avoided anyway.
For use cases like this, I typically go with the following approach.
Core support package for type filtering — for example, for classpath scanning.
Comment From: deejay1
@snicoll @sbrannen I reworded the doc strings a little bit, should be better now.
Comment From: sbrannen
This has been merged into main.
Thanks