Is it bad practice to access env parameters without going through the config?

Question

symfony

I am writing an automation for clicking pages in a browser using symfony 5.0. Pages are taken out in conditional PageObject classes. A number of pages need settings, which I pass through .env => config/services.yaml => class constructors. Bottom line - when I create a script for working with a page in a method of another class, then I need to pass all the parameters through the constructor of the script class. I read about setter injection, but it only works with class arguments, not regular string arguments.
Can I access these parameters directly through $_ENV inside the PageObject methods, thereby getting rid of passing parameters along the class chain, or is this option bad and more literate?

Answer 1

I would probably not advise doing this, because it, in fact, differs little from using global variables. Why not inject your script class into another class through a constructor in the same way? I think that this is the best solution, especially since you don’t have to write anything to the configs to implement your script class.