menu
Channels
Team

What's the point in having configureCurrentEnv in the BoosterApp interface?

May 27, 2020 at 8:57pm

What's the point in having configureCurrentEnv in the BoosterApp interface?

May 27, 2020 at 8:57pm
Screenshot 2020-05-27 at 21.55.25.png
Could it be removed from there to avoid users get confused?

May 28, 2020 at 11:11am
Good suggestion! Yep, that's mostly for internal use. From a user's perspective, it makes no sense. We can un-export it
  • reply
  • like

May 29, 2020 at 5:38pm

June 23, 2020 at 10:42am
Exactly, we had to export it because the cli package uses it. I think that it could make sense to replace this function that exposes the config via callback with a simpler Booster.config: Promise<BoosterConfig> that's not resolved until the configuration and current env are settled.
  • reply
  • like

August 10, 2020 at 5:01pm
private
This conversation has been locked