Add tlSkipIrrelevantScalas setting
#159
Merged
Conversation
This file contains 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
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.
Followup to #117. Closes #140.
#140 was initially concerning but it turned out the project where I saw that was misconfigured actually.
After experimenting with the snapshot I'm reasonably confident that for most projects this
skipthing works very nicely.There are certain situations where it may prove to be problematic, such as backpublishing tags for kind-projector or maybe in the community build which is specifically trying to build projects on a scala version not configured in the project build.
In any case, it would be foolish not to provide an escape-hatch.
This should be the last fix going into 0.4.4.I lied. I want to get some of the site-related stuff in.