Explicitly include libraries (opposite of stIgnore) #601
Comments
cornerman
added a commit
to cornerman/Converter
that referenced
this issue
Jun 8, 2024
If you only want to generate scalablytyped facedes for a few js depdendencies, you currently have to maintain an ignore list in the build.sbt file.
In order to make this more explicit and easier to maintain, this PR introduces a new option `stExplicitInclude`, which allows to explicitly select the libraries, you want to process. All others are automatically ignored.
Usage:
```
// is None per default
stExplicitInclude := Some(List("packageA", "packageB"))
```
fixes ScalablyTyped#601
cornerman
added a commit
to cornerman/Converter
that referenced
this issue
Jun 8, 2024
If you only want to generate ScalablyTyped facades for a few js dependencies, you currently have to maintain an ignore list in the build.sbt file.
In order to make this more explicit and easier to maintain, this PR introduces a new option `stExplicitInclude`, which allows to explicitly select the libraries, you want to process. All others are automatically ignored.
Usage:
```
// is None per default
stExplicitInclude := Some(List("packageA", "packageB"))
```
fixes ScalablyTyped#601
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Would you be open to a PR that adds a setting to explicitly include dependencies?
Right now, I have to
stIgnoreevery dependency that should not have a scalablytyped facade. But in order to keep the build.sbt more expressive, I would actually like to specify the packages that need a scalablytyped facade. Because otherwise I can only understand it together with the package.json.It could look like this (open for other name suggestions):
There are a few cases to handle though:
stIgnoreandstIncludeExplicitwould not compose well and should not be used together.The text was updated successfully, but these errors were encountered: