{"version":"2.1.284","anchor":"a-path-argument-check-no-longer-refuses-network-locations","canonical_anchor":"a-path-argument-check-no-longer-refuses-network-locations","heading":"A path check no longer rejects network locations","tier":"internal","area":"File Operations","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/a-path-argument-check-no-longer-refuses-network-locations","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### A path check no longer rejects network locations\n\nA shared check for operations that take a `path` now only confirms a path was given and no longer refuses network locations\n\n**Unclear.** It is not clear which feature these operations belong to, or whether network locations are now refused somewhere else instead.\n\n**What**\n\nSome operations take a `path` argument, including ones that read a file as text or bytes and ones that resolve a path. The shared check on that argument now only confirms that a path was given. Before, it also refused network locations with the message \"a network location is not reached from here\". That message is still used in other places.\n\n**Why**\n\nIn practice, network paths such as shared network drives can now get past this check for these operations.\n\n- Area: File Operations\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}