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
#1051 provides a convenient way to navigate sub-environments. I think it is necessary, but not sufficient, for a good UX.
activate +test (as opposed to activate test) also shows the intention of a user to use an environment as a subenv of the active environment. We can leverage this information to display better feedback to users.
For example: after running activate test, the user is shown (test) pkg>. You know that a test environment is activated, but you don't know what environment that test environment applies to.
We can change this feedback to something like (Foo:test) pkg>.
+ subenv syntax is more general than testing. If #1085 is implemented, I can image a workflow along these lines:
(Foo) pkg> activate +feature/A
(Foo:A) pkg> add Bar
(Foo:A) pkg> test
(Foo:A) pkg> activate -
(Foo) pkg>
Don't mean to get ahead of myself 😁. Just something to consider if/when we get to that point.
The text was updated successfully, but these errors were encountered:
#1051 provides a convenient way to navigate sub-environments. I think it is necessary, but not sufficient, for a good UX.
activate +test
(as opposed toactivate test
) also shows the intention of a user to use an environment as a subenv of the active environment. We can leverage this information to display better feedback to users.For example: after running
activate test
, the user is shown(test) pkg>
. You know that a test environment is activated, but you don't know what environment that test environment applies to.We can change this feedback to something like
(Foo:test) pkg>
.+
subenv syntax is more general than testing. If #1085 is implemented, I can image a workflow along these lines:Don't mean to get ahead of myself 😁. Just something to consider if/when we get to that point.
The text was updated successfully, but these errors were encountered: