`dart create` in the current directory works differently from `flutter create`

[gspencergoog]

Description

If the LLM calls create project with "." for the directory, the Flutter version will just happily call flutter create . and things work. If you do this for a Dart project, it will fail because:

Directory
'/usr/local/google/home/user/code/my_project/.'
already exists (use '--force' to force project generation).          

Which makes me think that the Dart version should automatically use --force if the argument is '.' or something. That would have side effects, though. For instance, if your cwd already has a README.md, then the --force would cause it to be overwritten instead of left alone, as the flutter command would.

Probably the real fix is that dart create . should not fail like it currently does, and might need a flag to let it act more like flutter create and not touch files that already exist.

[jakemac53]

Yeah I think this should be an issue for the SDKs to align the behavior of these commands?

[jakemac53]

cc @bkonyi for thoughts