{"version":"2.1.224","anchor":"trailing-slashes-no-longer-change-glob-permission-warnings-o","canonical_anchor":"trailing-slashes-no-longer-change-glob-permission-warnings-o","heading":"Trailing slashes no longer change glob-permission warnings on Linux","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/trailing-slashes-no-longer-change-glob-permission-warnings-o","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Trailing slashes no longer change glob-permission warnings on Linux\n\nTrailing slashes in Read and Edit permission rules no longer change the wildcard warning on Linux.\n\n**What**\n\nThe check that warns about wildcard patterns in Read and Edit permission rules now strips trailing slashes from deny rules and absolute paths before looking for wildcards, so `\/foo\/bar\/` and `\/foo\/bar` behave the same. Allow and deny rules are walked as tagged pairs. Linux and WSL only; other platforms produce no warnings.\n\n**Evidence**\n\n`Failed to get Linux glob pattern warnings: `\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}