feat: introduce update-ts-reference.yaml #34
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
MKruschke
force-pushed
the
feat-introduction-of-a-config-file
branch
2 times, most recently
from
83c6345
to
c4fa54a
Compare
MKruschke
force-pushed
the
feat-introduction-of-a-config-file
branch
from
c4fa54a
to
586d508
Compare
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.
This allows a config file to specify paths to the packages in case there is no package.json or pnp-workspace.yaml in the root as described in the feature request #31 . Additionally, it allows you to expand the workspace path configuration in case you want to include more packages that are not inside the usual workspace configuration.