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.

Sign up for GitHub

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

Jump to bottom

#17542 enabling forceConsistentCasingInFileNames by default #27464

Closed
wants to merge 4 commits into from
Closed

#17542 enabling forceConsistentCasingInFileNames by default #27464

wants to merge 4 commits into from

Commits on Sep 30, 2018

  1. forceConsistentCasingInFileNames does not need to be specified anymore 

    it is now on by default. See microsoft#17542
    @Almenon
    Almenon authored Sep 30, 2018
    Configuration menu
    Copy the full SHA
    92d7293 View commit details
    Browse the repository at this point in the history

  2. microsoft#17542 enabling case sensitivty by default 

    This implements microsoft#17542 enable forceConsistentCasingInFileNames by default which fixes cross-platform compatability issues due to typescript not reporting different cases as an error in windows.

Making change in right repo & branch this time >_<
    @Almenon
    Almenon authored Sep 30, 2018
    Configuration menu
    Copy the full SHA
    65daa26 View commit details
    Browse the repository at this point in the history

  3. making linter changes

    @Almenon
    Almenon authored Sep 30, 2018
    Configuration menu
    Copy the full SHA
    31ab96f View commit details
    Browse the repository at this point in the history

Commits on Jan 25, 2019

  1. get rid of null check 

    options.forceConsistentCasingInFileNames can't be null here
    @Almenon
    Almenon authored Jan 25, 2019
    Configuration menu
    Copy the full SHA
    42461e1 View commit details
    Browse the repository at this point in the history