{"version":"2.1.246","anchor":"editing-a-file-in-a-denied-directory-gets-its-own-error","canonical_anchor":"editing-a-file-in-a-denied-directory-gets-its-own-error","heading":"Editing a file in a denied directory gets its own error","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/editing-a-file-in-a-denied-directory-gets-its-own-error","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Editing a file in a denied directory gets its own error\n\nTouching a file in a directory your settings exclude now says exactly that, not a generic denial.\n\n**What**\n\nAttempts to read or write a file under a directory excluded by your permission settings now say so directly instead of falling back to the generic deny-rule wording.\n\n**Details**\n\n- Fixed string, no gate, sitting beside the existing read-deny messages.\n\n**Evidence**\n\n`File is in a directory that is denied by your permission settings.`\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}