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

Issue template: Recommend to run tsc directly #17246

Merged
2 commits merged into from
Jul 17, 2017
Merged

Issue template: Recommend to run tsc directly #17246

2 commits merged into from
Jul 17, 2017

Conversation

ghost
Copy link

@ghost ghost commented Jul 17, 2017

Sometimes we see issues that only reproduce in a certain build environment, such as webpack or visual studio. This leads to confusion when we can't reproduce the user's issue. This would ask people to try reproducing the issue with tsc.

@ghost ghost requested review from sandersn and RyanCavanaugh July 17, 2017 16:45
@@ -8,7 +8,7 @@

```ts
// A *self-contained* demonstration of the problem follows...

// Test this by running `tsc` on the command-line, rather than through another build tool.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

through another build tool such as Gulp, Webpack, etc.

@DanielRosenwasser DanielRosenwasser changed the title Issue template: Recommand to run tsc directly Issue template: Recommend to run tsc directly Jul 17, 2017
@ghost ghost merged commit de9a67f into master Jul 17, 2017
@ghost ghost deleted the issue_tsc branch July 17, 2017 21:45
@microsoft microsoft locked and limited conversation to collaborators Jun 14, 2018
This pull request was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants