-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
list all environments on local machine (flox envs) #934
Comments
+1 from user research today |
Sample implementation in #988 |
@ysndr @ghudgins apologies for the slowness here. I wanted to take a holistic look before introducing a new command. |
@jennymahmoudi can you validate this from the design/product side? |
On the
A few more related things, not sure if they are handled separately or not:
|
done
TBF there are two examples if this in the notion:
lets go with But is it then Besides, ✨ was defined as the emoji for a "created" message, do we need to have another look at the emoji guidelines, maybe use
added, let me know if the command should go into the main section instead, for now its under Additional Commands
yep forgot about that, added now |
My thinking at the time was to differentiate the Active list from the Inactive list with the sparkle, so when there was just one list (
I don't think we need to pick a different emoji. Some emojis will be reserved for specific situations (like the ❌ for errors and 🗑️ for delete), just like some colors in FloxHub are (like red for errors). But I think emojis like ✨ can be used for multiple scenarios for emphasis, similar to how a primary color or other text styling like bold can be used throughout FloxHub. If this causes any confusion between init and activate, we can revisit.
Additional commands makes sense. 👍 |
looks good! |
When I don’t remember what environments I’ve created,
I need a way to see where all my environments are
So I can navigate to the directory with the environment I want
AND I can copy and paste the directory path to use with
--dir
When I am looking at a list of my local and managed environments,
I need to quickly see which environments are activated,
So I can check that it’s working as I expected.
Acceptance Criteria
flox envs
: shows local env names (w/owner if managed) and their path; show active envs in a list first, with the most recently activated env in boldgit pull
but not yet usedflox envs --active
: shows only active envsflox envs --json
: active and inactive environments and all their info in JSON formatflox envs --active --json
: contents of_FLOX_ACTIVE_ENVIRONMENTS
- only active environments and all their infoSee Notion for output for each command:
https://www.notion.so/floxdev/View-environments-CLI-design-8f68c6465e944cba8f3ab474b1785ca4?pvs=4#f36eea0623564801a7ec717f11203c65
The text was updated successfully, but these errors were encountered: