You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What seems a bit weird to me is that "stack" configuration, so basically project's environment configuration, is stored outside the project. I cannot understand this decision. Shouldn't projects be possibly self-contained? The fewer dependencies the better, right? So why the project's codebase needs dependency on the stack configuration stored in the global directory? What if a new developer will set up their project, and get a different stack files downloaded than the rest of the team is using, because the stack repository has been updated in a meantime? I'm so confused by this setup.
The text was updated successfully, but these errors were encountered:
What seems a bit weird to me is that "stack" configuration, so basically project's environment configuration, is stored outside the project. I cannot understand this decision. Shouldn't projects be possibly self-contained? The fewer dependencies the better, right? So why the project's codebase needs dependency on the stack configuration stored in the global directory? What if a new developer will set up their project, and get a different stack files downloaded than the rest of the team is using, because the stack repository has been updated in a meantime? I'm so confused by this setup.
The text was updated successfully, but these errors were encountered: