Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[api-extractor] Allow for loading the ExtractorConfig without validating existence of target typings #3472

Merged
merged 6 commits into from
Jun 27, 2022

Conversation

D4N14L
Copy link
Member

@D4N14L D4N14L commented Jun 15, 2022

Summary

Allow for loading the ExtractorConfig without validating existence of target typings.

Details

There are some scenarios where loading up the API-Extractor configuration is required prior to the existence of the typings files that API Extractor sources from (such as obtaining output folder paths and ensuring they are empty). This PR adds the option ignoreMissingConfigTargets which can be passed into the ExtractorConfig options at load time to avoid validating the existence of the target files.

How it was tested

Forked off of PR #3468 where it was tested extensively against the rest of the Rushstack monorepo.

apps/api-extractor/src/api/ExtractorConfig.ts Outdated Show resolved Hide resolved
apps/api-extractor/src/api/ExtractorConfig.ts Outdated Show resolved Hide resolved
apps/api-extractor/src/api/ExtractorConfig.ts Outdated Show resolved Hide resolved
@D4N14L D4N14L enabled auto-merge June 27, 2022 19:38
@D4N14L D4N14L merged commit 00f1dfa into microsoft:main Jun 27, 2022
@iclanton iclanton deleted the user/danade/ApiExtractorConfigLoad branch June 28, 2022 02:27
Qjuh pushed a commit to discordjs/rushstack that referenced this pull request Nov 7, 2023
…rConfigLoad

[api-extractor] Allow for loading the `ExtractorConfig` without validating existence of target typings
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants