Problem/Motivation
Now that recipes are in core, we need to update the drupal/recommended-project composer template so users can require recipes using composer.
Proposed resolution
1. Add a drupal-recipe installer type.
We are going to need this until https://github.com/composer/installers/pull/534 is merged. It doesn't look like a very active project.
Its been merged and a new release has been cut.
2. Add an installer-path for drupal-recipe
Remaining tasks
Merge request added.
User interface changes
N/A
API changes
N/A
Data model changes
N/A
Release notes snippet
N/A
| Comment | File | Size | Author |
|---|---|---|---|
| #28 | 3447886-nr-bot.txt | 90 bytes | needs-review-queue-bot |
| #24 | 3447886-nr-bot.txt | 90 bytes | needs-review-queue-bot |
Issue fork drupal-3447886
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
- 3447886-add-recipes-to-template
changes, plain diff MR !8113
- 3447886-add-support-for
compare
Comments
Comment #2
thejimbirch commentedComment #5
thejimbirch commentedMerge request added.
Comment #6
jnicola commentedLooks good to me! Could you elaborate on some ways to test?
Comment #7
simeI'm unable to make this work just by setting
"installer-types": ["drupal-recipe"],. Does it need oomphinc/composer-installers-extender?Comment #8
thejimbirch commentedYes, thanks! I am not sure core maintainers would want that. If not, we can remove and postpone on the composer/installers pull request.
Comment #9
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #10
thejimbirch commentedThe test failed because of cspell on
oomphinc.It looks like Drupal core uses inline comments in files to exclude words from cspell.
But comments aren't allowed in JSON files, so I am not sure how to fix this. Any ideas?
Comment #11
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #12
simeIt looks like you can add it here, for example egulias is from a package from memory https://github.com/drupal/core/blob/11.x/misc/cspell/dictionary.txt#L218
Comment #13
thejimbirch commentedThanks! Lets see what the bot thinks of this now.
Comment #14
smustgrave commentedCan this be rebased for the failures?
Comment #15
smustgrave commentedComment #16
simeReplicated the current error locally, but i'm not really sure why this fails, none of the usual cases seems to apply. If i copy the composer.json to a new directory and run
composer updateit builds fine. Something about the test context?Comment #17
simeNot related to above, but I think it might also need to be added to allowed plugins section?
Comment #18
thejimbirch commentedComment #19
thejimbirch commentedComment #20
phenaproximaTo do this, we also need to bump the composer/installers requirement to ^2.3.
Comment #21
thejimbirch commentedNice catch, thanks! Updated it.
Comment #22
thejimbirch commentedComment #23
alexpottDo we want to scaffold a readme file?
Comment #24
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #25
alexpottComment #26
phenaproximaNot seeing anything obviously wrong here...let's do it!
Comment #27
phenaproximaComment #28
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #29
alexpottComment #31
catchCommitted/pushed to 11.1.x, thanks!
If we want to add this to 10.4.x, it'll need a separate MR, but marking fixed for now.
Comment #33
alexpottCrediting @thejimbirch - thanks for the initial work on this one!
Comment #35
tr commentedThis commit caused a problem with contributed module testing. Please read #3495586: PHPCS error in contributed module caused by core recipe.README.txt and comment there about whether
recipe.README.txtis intentionally being copied into[project-root](and if so, why?), or whether it should be copied into[web-root]instead.