| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
Can you add a cc test for testing only this function and every edge case you're targeting?
Sorry, something went wrong.
|
@anonrig would you mind restarting the Github CI now that #54391 landed? Actually I'm going to rebase for it. |
Sorry, something went wrong.
Codecov ReportAttention: Patch coverage is 80.00000% with 2 lines in your changes missing coverage. Please review.
@@ Coverage Diff @@
## main #54385 +/- ##
==========================================
- Coverage 87.08% 87.07% -0.01%
==========================================
Files 648 648
Lines 182341 182338 -3
Branches 34982 34981 -1
==========================================
- Hits 158783 158773 -10
- Misses 16831 16833 +2
- Partials 6727 6732 +5
|
Sorry, something went wrong.
|
@anonrig Do you think this should land (eventually), or it should be held-off, and a redone GetPathFromArgs would be better, one that doesn't have these edge cases? |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This PR replaces the old while loop with a newer for loop.
Fixes the following edge cases:
node script.js --env-file .env node --env-file-ABCD .env node -- --env-file .env node -invalid --env-file .env # this will error, but the env file is still processedUnfortunately, this introduces an edge case where some argument parameters, such as --eval <...> cause any future --env-file arguments to be ignored.
Fixes #54255
Fixes #54232
Related to #54237