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

Add tip re. --project option in VSCode config #738

Merged
merged 2 commits into from
Feb 9, 2019
Merged

Add tip re. --project option in VSCode config #738

merged 2 commits into from
Feb 9, 2019

Conversation

Zlatkovsky
Copy link
Contributor

Add a tip in the README to recommend how developers can pipe the --project commandline option into a VSCode config.

Inspired by trying and failing to find this info, and ultimately opening a bug about it, which contained the workaround. #734 (comment)

@coveralls
Copy link

Coverage Status

Coverage remained the same at 84.946% when pulling 4a2f697 on Zlatkovsky:patch-1 into d58488b on TypeStrong:master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage remained the same at 84.946% when pulling 4a2f697 on Zlatkovsky:patch-1 into d58488b on TypeStrong:master.

@coveralls
Copy link

coveralls commented Nov 27, 2018

Coverage Status

Coverage increased (+0.9%) to 85.825% when pulling 3715255 on Zlatkovsky:patch-1 into d58488b on TypeStrong:master.

@blakeembrey blakeembrey merged commit efaf67a into TypeStrong:master Feb 9, 2019
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.

3 participants