deno/tests/testdata/run/env_file_missing.out

Warning The `--env` flag was used, but the environment file specified 'missing' was not found.
undefined
undefined
undefined
fix: `--env` flag confusing message on syntax error (#23915) Enhanced warning message for --env flag with run and eval subcommands. The commit is specifically made to address issue #23674 by improving the warning messages that appear when using the --env flag with run or eval subcommands in the following scenarios: 1. Missing environment file. 2. Incorrect syntax in the environment file content. Changes made - Distinguishes between cases of missing environment file and wrong syntax in the environment file content. - Shows a concise warning message to convey the case/issue occurred. Code changes & enhancements - Implemented a match statement to handle different types of errors received while getting and parsing the file content to display a concise warning message, rather than simple error check and then displaying the same warning message for whatever the type of error is. - Updated the related existing tests to reflect the new warning messages. - Added two test cases to cover the wrong environment file content syntax with both run and eval subcommands. Impact The use of --env flag with both run/eval would be more user-friendly as it gives a precise description of what is not right when using incorrectly. If you could give it a look, @dsherret , I appreciate your feedback on these changes. --------- Co-authored-by: Bartek Iwańczuk <biwanczuk@gmail.com> 2024-05-27 16:06:18 +03:00			Warning The `--env` flag was used, but the environment file specified 'missing' was not found.
refactor: don't error when `.env` is not present (#21879) Uses similar format to when the latest version of std is implicitly being used. Closes #21788 2024-01-22 10:27:14 +11:00			`undefined`
			`undefined`
			`undefined`