Open joshsedl opened 1 year ago
There are several issues, with the drowl-init-from-existing command. One of the biggest issues is, that it currently doesn't use the remote projects "settings.php". This leads to several issues, e.g. https://github.com/webksde/ddev-vscode-devcontainer-drupal-template/issues/67.
As long as we do not let the user provide the "settings.php" and initiate the project, based on its values, I will disable the command, as it is very unreliable.
When trying to fix this problem, we should also, work on other "dife" issues, see: https://github.com/webksde/ddev-vscode-devcontainer-drupal-template/issues?q=is%3Aissue+is%3Aopen+drowl-init-from-existing
Rarely used, so maybe hiher priority than other issues, but not really high priority in total.
Yea, maybe disabling it entirely, could be a bit too much, but yea
There are several issues, with the drowl-init-from-existing command. One of the biggest issues is, that it currently doesn't use the remote projects "settings.php". This leads to several issues, e.g. https://github.com/webksde/ddev-vscode-devcontainer-drupal-template/issues/67.
As long as we do not let the user provide the "settings.php" and initiate the project, based on its values, I will disable the command, as it is very unreliable.
When trying to fix this problem, we should also, work on other "dife" issues, see: https://github.com/webksde/ddev-vscode-devcontainer-drupal-template/issues?q=is%3Aissue+is%3Aopen+drowl-init-from-existing