{"version":"2.1.271","anchor":"new-sdk-url-resolution-path-via-rxn-bypassing-argv-p","canonical_anchor":"new-sdk-url-resolution-path-via-rxn-bypassing-argv-p","heading":"New --sdk-url resolution path via RXn() bypassing argv parsing","tier":"internal","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/new-sdk-url-resolution-path-via-rxn-bypassing-argv-p","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### New `--sdk-url` resolution path via `RXn()` bypassing argv parsing\n\nThe --sdk-url value can now be supplied through a new internal path that bypasses normal argument parsing\n\n**Unclear.** What supplies the value through this new path, and in what situation it would differ from the argument-scanning fallback, isn't stated.\n\n**What**\n\nThe internal function that resolves the `--sdk-url` command-line flag now checks a separate function first, and if it has a value, uses that directly instead of scanning the command-line arguments as before. The old argument-scanning behavior still runs as a fallback if that first check comes back empty.\n\n**Why**\n\nThis gives `--sdk-url` an additional way to be set that doesn't depend on how the process was launched with command-line arguments, likely useful for cases where the value needs to be supplied programmatically rather than typed on a command line.\n\n- Area: SDK\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}