As I said in the title, I don't understand why the 'dotenv()' and 'dotenv_iter()' methods are made to behave differently.
When I do 'dotenv::dotenv()', I get the system environment, and when I do 'dotenv::dotenv_iter()', I only get the .env file.
I couldn't find an explanation anywhere.
Therefore, I propose a method similar to dotenv_values in python.
As I said in the title, I don't understand why the 'dotenv()' and 'dotenv_iter()' methods are made to behave differently.
When I do 'dotenv::dotenv()', I get the system environment, and when I do 'dotenv::dotenv_iter()', I only get the .env file.
I couldn't find an explanation anywhere.
Therefore, I propose a method similar to dotenv_values in python.