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

feat: expand api w/ .forProject(string),.withTsConfig(string|TsConfig) #561

Merged
merged 1 commit into from
Jan 27, 2018

Conversation

dherges
Copy link
Contributor

@dherges dherges commented Jan 27, 2018

I'm submitting a...

[ ] Bug Fix
[x] Feature
[ ] Other (Refactoring, Added tests, Documentation, ...)

Checklist

  • Commit Messages follow the Conventional Commits pattern
    • A feature commit message is prefixed "feat:"
    • A bugfix commit message is prefixed "fix:"
  • Tests for the changes have been added

Description

Closes #557

Does this PR introduce a breaking change?

[ ] Yes
[x] No

@dherges dherges changed the title feat: expand api to .withTsConfig(string|TsConfig), .forProject() feat: expand api w/ .forProject(string),.withTsConfig(string|TsConfig) Jan 27, 2018
@ng-packagr ng-packagr deleted a comment from TravisBuddy Jan 27, 2018
@dherges dherges merged commit 48f3569 into master Jan 27, 2018
@dherges dherges deleted the api-tsconfig-project branch January 27, 2018 14:08
@github-actions
Copy link

This PR has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

This action has been performed automatically by a bot.

@github-actions github-actions bot locked and limited conversation to collaborators Jun 19, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

withTsConfig accepts a ParsedConfiguration?
1 participant