feat: allow very_good create .

[a-wallen]

Status

READY/IN DEVELOPMENT/HOLD
READY

Description

Allows . as a project name (like flutter create .)

Type of Change

• ✨ New feature (non-breaking change which adds functionality)
• 🛠️ Bug fix (non-breaking change which fixes an issue)
• ❌ Breaking change (fix or feature that would cause existing functionality to change)
• 🧹 Code refactor
• ✅ Build configuration change
• 📝 Documentation
• 🗑️ Chore

[a-wallen]

fixes #969

[a-wallen]

this is ready for review.

by the way, the repo had 37 broken tests when I cloned it on my machine. I was wondering if I should submit those as issues.

[tomarra]

Fixed the formatting issue by updating from main via #1003 so CI is now passing. @wolfenrain can we get a review here?

[alestiago]

Pinging @wolfenrain

[wolfenrain]

LGTM, sorry for the late follow-up on my part. I will try and test out this branch later today to make sure it is backwards compatible but from the looks of it we should be good!

[a-wallen]

sure thing, let me know if there's anything I need to do.

[wolfenrain]

sure thing, let me know if there's anything I need to do.

The CI seems to be failing on some tests, mind having a look at that? I suspect that the tests are failing because of wrong parameters (might mean it isnt backwards compatible like we hoped?)

[a-wallen]

I can't tell which tests are failing. See this issue for more details #1162

[tomarra]

I can't tell which tests are failing. See this issue for more details #1162

Take a look at the details of the Actions output here. You can see the failing tests in the output.

[marcossevilla]

hey @a-wallen, can you take a look at the CI failures so we can merge this? thanks!

[marcossevilla]

hey @a-wallen! do you need any help with this? I'd be happy to help you move past the finish line 👍

[matiasleyba]

We are updating the very_good_templates to support this feature.
I'll move this PR to draft until we have all the templates updated and then I will finish the implementation of this feature.

[matiasleyba]

After discussing the feature, we've updated the CLI to allow . as a valid project name to create a project in the current directory, without wrapping it in a new folder. However, the project_name parameter will no be treated as a path.

✅ Accepted commands:

• very_good create dart_package my_package
  → Creates the project in ./my_package (same behavior as before).

Screen.Recording.2025-07-28.at.11.20.54.AM.mov

• very_good create dart_package .
  → Creates the project in the current directory (New).

Screen.Recording.2025-07-28.at.11.23.31.AM.mov

• very_good create dart_package my_package --output-directory path/to
  → Creates the project in path/to/my_package.

Screen.Recording.2025-07-28.at.11.24.51.AM.mov

❌ Invalid commands (will result in an error):

• very_good create dart_package . --output-directory path/to
  (Using . with --output-directory is not supported)

• very_good create dart_package path/my_package --output-directory path/to
  (project_name must not include a path)

ℹ️ Note: A following PR will include updates on the site documentation.