{"version":"2.1.227","anchor":"identically-written-scripts-are-no-longer-classified-as-one","canonical_anchor":"identically-written-scripts-are-no-longer-classified-as-one","heading":"Identically-written scripts are no longer classified as one","tier":"notice","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/identically-written-scripts-are-no-longer-classified-as-one","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Identically-written scripts are no longer classified as one\n\nTwo scripts with identical contents but different paths are no longer treated as the same.\n\n**What**\n\nThe workflow and script classifier now sees the script body followed by its path or name, rather than just one of the three. Two scripts with the same contents but different paths now classify separately.\n\n**Evidence**\n\n`toAutoClassifierInput(e) {`\n\n- Area: Telemetry\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}