feat: add max_configs_to_run param #62
Open
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
|
Will try to get to this this weekend - thanks for the PR! |
|
@dmmulroy Hey is there anything I can help you with to get this reviewed? :) |
dmmulroy
requested changes
Jan 29, 2025
|
@svenrisse so sorry this got drowned out in my notifications |
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.
Add a
max_configs_to_run(somebody got a better name?) param that defaults to previously hardcoded20to allow plugin user to increase the number of allowedtsconfigfiles.My monorepo has 26
tsconfigfiles and I was prohibited by the set max of20to run:TSC.Or is there a specific to reason to not go over 20 files?
Thanks for the great work on this plugin.