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
Hello, thanks for the great dev tools. And I noticed that installsAfter was introduced in order to reuse features, but only on that basis with feature execution sequence constraints that do not force users to install dependent features, this causes the downstream feature to implement some of the environment script commands that the upstream feature has already installed. For example, if you install the GIT command, which actually complements the Git feature constraint on installsAfter, if you implement the Git installation-related command in the downstream feature script, that's not necessary in my opinion, and if there is a specific version of Git installed on top, it is not necessary to run redundant Git installation commands downstream.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello, thanks for the great dev tools. And I noticed that installsAfter was introduced in order to reuse features, but only on that basis with feature execution sequence constraints that do not force users to install dependent features, this causes the downstream feature to implement some of the environment script commands that the upstream feature has already installed. For example, if you install the GIT command, which actually complements the Git feature constraint on installsAfter, if you implement the Git installation-related command in the downstream feature script, that's not necessary in my opinion, and if there is a specific version of Git installed on top, it is not necessary to run redundant Git installation commands downstream.
Beta Was this translation helpful? Give feedback.
All reactions