scala_doc: Export ScaladocAspectInfo to allow users to build custom scaladoc aspects #1404
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Export
ScaladocAspectInfoto allow users to provide custom aspect implementation tomake_scala_doc_ruleMotivation
Some of our scala rules require extra jars to be present on the classpath because of custom rules present in our repo. Its hard to replicate this requirement in tests (#1393 for more information). Exporting the
ScaladocAspectInfohelps us build a custom aspect implementation formake_scala_doc_rulebased on some of the custom rules in our repo.