Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Follow-up from #2113659: Routing YAML for devel_generate .
changed module_exists to Drupal::moduleHandler()->moduleExists as per https://drupal.org/node/1894902
Comment | File | Size | Author |
---|---|---|---|
#9 | 2116375-9-module_exists.patch | 9.57 KB | joelpittet |
#4 | 2116375-4-module-exists-static-method.patch | 9.39 KB | joelpittet |
#1 | 2116375-module_exists-replace.patch | 5.84 KB | joelpittet |
Comments
Comment #1
joelpittetHere's the patch.
Comment #2
joelpittetpostponed and will need a re-roll after this gets in:
#2113659: Routing YAML for devel_generate
Comment #3
pcambraComment #4
joelpittetMight as well do this in one shot as there isn't much in other components.
Comment #5
pcambraFor some reason, tests are stuck again :\
Comment #6
joelpittetStuck how?
Comment #8
salvisI reset the repo tests and they're green again.
Before patch tests can run, the version in the repository must pass, i.e. https://drupal.org/node/3236/qa must be green. Whenever we push something, the testbot runs the repo test for the corresponding branch, and if the test fails, then patch testing is suspended.
I'm not sure whether repo testing continues automatically or not. IAC, it happens occasionally that d.o doesn't catch the answer from qa.d.o, and the repo tests won't turn green anymore. In that situation you have to delete and re-request them, which I did a couple of hour ago. After that, patch testing should resume.
However, #4 seems to be stuck on its own. But when you click the [View] link, you see that it failed.
Comment #9
joelpittetThanks for the detailed notes. Still a bit fuzzy on it but I see that it's green but viewing the test failed to apply patch.
So here's a re-roll.
Comment #10
pcambraNot in the routing files please :)
Comment #11
pcambraComment #12
joelpittet@pcambra I was told that's how it is done... when you wrap the menu items wouldn't you want to also stop the routes from being created without that module as well? Maybe there is another way?
Comment #13
pcambraIs this the way to do it? Looks a really odd thing to put in a yaml file
Comment #14
amateescu CreditAttribution: amateescu commentedFrom what I see in https://drupal.org/node/1800686#requirements, _module_exists in routing files has to be _module_dependencies.
Comment #15
joelpittet@amateescu that does look right @pcambra mind if I change it to that?
_module_dependencies
Comment #16
pcambraAfter some changes I pushed this in, thanks @joelpittet, @amateescu