dx new in existing multicrate workspace about dioxus HOT 1 OPEN

I'm reading cargo-metadata, but nothing is jumping out at me to say "this is a workspace" vs "this is a standalone package.

Maybe checking the length of workspace_members, and if there's only 1 checking if it matches the workspace_root?

I'm thinking of use cases/edge cases though;

• A user runs dx new - their current directory is outside any cargo workspace
  • This is as-is, and should predictably make the directory and run cargo fmt as well as the rest of the flow
• A user runs dx new - their current directory is a multi-crate cargo workspace
  • This is the flow I just ran, and everything is made fine (I just had to add the new crate to package members), I'd like to avoid this manual work if possible.
• A user runs dx new - their current directory is a single rust crate
  • This produces the directory, but possibly isn't what the user expected? (Not sure what I'd expect here)

from dioxus.