Best practices on how to boot dependescies based on env


I will like to boot ‘real’ dependencies in production env and ‘fake’ ones on development and test env. Did you tried that before? How did it worked out?

Such feature is not supported. Feel free to report a feature request and we could discuss it there. For now you’d have to use a custom component loader that would look at environment and decide which dependency should be loaded.

Got it, request features happens in github?

I am basically doing a bunch of case statements a lot :frowning:

yes please

yeah as I said, we have some building blocks to enable this, but it’s not a 1st-class feature yet.