Improve the behavior of ddev config
on an existing project with an invalid project type
#5146
Closed
1 task done
Labels
Is there an existing issue for this?
Is your feature request related to a problem?
When switching back to the HEAD version from the silverstripe PR version i completely forgot for one project that it was created in silverstripe. I ran
ddev config
for that project and the output was the following:i just pressed return accepting silverstripe. the output returned was:
three problems first the output is twice. the first time correclt stating silverstripe is not a valid project type. the second time using
Project Type [%s] (%s)
. the first time the last output is wordpress without silverstripe the second time the last output is wordpresssilverstripe and the cursor for text input is right after thee
of silverstripe.Describe your solution
After a none existing project type is submitted i would return:
Describe alternatives
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: