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

feat: no-restricted-imports support casing #15439

Merged
merged 3 commits into from Jan 15, 2022
Merged

feat: no-restricted-imports support casing #15439

merged 3 commits into from Jan 15, 2022

Commits on Jan 5, 2022

  1. fix: no-restricted-imports support casing 

    Path matching in `.gitignore` can be case-sensitive, and
ignore@5.2.0 supports this as well as maintains support for
relative paths, whose support was dropped after 4.0.6 but
restored in 5.2.0 (this was a blocker for past upgrades).

By default, this rule remains case-insensitive to maintain
backwards compatibility with earlier versions. Only by explicitly
specifying it in a custom pattern object can it be triggered.
    @gfyoung
    gfyoung committed Jan 5, 2022
    Copy the full SHA
    fbf2438 View commit details
    Browse the repository at this point in the history

  2. Set allowRelativePaths directly in files 

    Per member feedback, the allowing of relative paths
was not entirely intentional for rules using the
`ignore` library. This commit also reverts the
utility for creating `ignore` instances.
    @gfyoung
    gfyoung committed Jan 5, 2022
    Copy the full SHA
    0441caf View commit details
    Browse the repository at this point in the history

  3. Update word in docs for allowRelativePaths 

    Per reviewer feedback
    @gfyoung
    gfyoung committed Jan 5, 2022
    Copy the full SHA
    aec159f View commit details
    Browse the repository at this point in the history