Macro alternative to fallback to regular env

[ShayBox]

I use dotenvy! for development to load from .env and env! in production to load from regular env (GitHub Workflows), now I have a feature flag to switch between the two but it's very inconvenient and repetitive.

#[cfg(feature = "production")]
const EXAMPLE_ENV: &str = dotenv!("EXAMPLE_ENV");
#[cfg(not(feature = "production"))]
const EXAMPLE_ENV: &str = env!("EXAMPLE_ENV");

Having a macro that falls back to the regular env would be nice.

[DaXcess]

+1

I was initially under the impression that this was already how dotenvy operated, but unfortunately had to find out the hard way that environment variables in the build pipeline were not accepted by the dotenv! macro, as it throws a compiler error when no .env file is found, even when the environment variable is present.