Less smart Drupal core version detection #46
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue discussion at #38
This is my proposal for version detection. Default to 10 (until 11 is released), and ask user to override via ddev config as needed. No more looking at DDEV_PROJECT_TYPE.
I'm unsure how best to override the env variable that this project's config.contrib.yaml. Supplies. Can user do that in their project's config.yaml, or do they need to create a config.zz.yaml?