-
-
Notifications
You must be signed in to change notification settings - Fork 721
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
dx new in existing multicrate workspace #2350
Labels
Comments
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;
|
ealmloff
added
enhancement
New feature or request
cli
Related to the dioxus-cli program
labels
Apr 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Request
When creating a new project with
dx new
, after the directory is createdcargo fmt
is ran. If this is in a workspace where the user has not pre-added the crate to workspace members list, the user is presented with a cargo fmt error message.Everything else runs fine, and the command has an exit code of 0, as everything is fine, it just looks worrying.
Implement Suggestion
Not sure how possible it is, currently investigating, but if the user is in a workspace either
The text was updated successfully, but these errors were encountered: