Closed (fixed)
Project:
Mailchimp
Version:
8.x-1.x-dev
Component:
General
Priority:
Normal
Category:
Task
Assigned:
Issue tags:
Reporter:
Created:
23 Mar 2019 at 22:52 UTC
Updated:
28 Jan 2021 at 00:16 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
sergiu stici commentedComment #3
driverok commentedComment #4
amateichuk commentedComment #5
amateichuk commentedPlease check
Comment #6
berdirno need for implicit true argument, and it would need to be TRUE
remove the old code, don't just comment it out.
variable names should be improved, $entity_type_manager and also $view_builder, render_controller is a very old name for this. not directly related, but we touch this line anyway.
Additionally, the simpletest tests should be converted to functional tests, and we should add core_version_requirement per https://www.drupal.org/node/3070687.
Comment #7
amateichuk commentedFixed problems, besides tests
Comment #8
primsi commented@Tolyan4ik did you plan to work on the tests part too? Otherwise I can.
Comment #9
primsi commentedWent ahead and did that bit.
drupal-check now returns only the lib parts, which we don't need/cant fix?
Comment #10
berdirYes, the included library has a separate issue.
multi-assignments are afaik kinda against drupal coding standards, also this seems unrelated as we don't actually change anything here. I also don't understand why it does that loop and doesn't just set $entity_type = $matches[1] and so on. But, again, out of context, lets avoid changing that :)
render() is not actually deprecated but shouldn't really be used anymore. But a bit out of scope, also as it gets tricky as to where we should stop, comparing with how e.g. \Drupal\media\Plugin\Filter\MediaEmbed works, this doesn't handle translation, placeholders and so on. So, lets do the minimum here.
nitpick: unnecessary extra newline.
same.
Comment #11
primsi commentedThx. Addressed.
Comment #12
berdirRunning the tests manually gives me the following dynamic deprecation messages:
Additionally, we need to do core_version_requirement in all info.yml files and also update composer.json as documented in https://www.drupal.org/node/3070687. And we probably want to specifiy ^8.7.7 || ^8 and remove core: 8.x.
Comment #13
primsi commented> Entity type "mailchimp_signup" is using config schema as a fallback for a missing `config_export`
Not sure if I did that bit correctly, there are differences between \Drupal\mailchimp_signup\Entity\MailchimpSignup and mailchimp_signup.schema.yml
> probably want to specifiy ^8.7.7 || ^8
I guess you meant "^8.7.7 || ^9" here?
Comment #14
primsi commentedAdding the missing schema properties to the annotation.
Comment #15
berdirthis is missing the new key.
it kinda is optional for test modules now, but only in 8.8
same
I'm not sure what's up with test bot.
Comment #16
primsi commentedAdding.
Comment #17
berdirOk, I just realized what the problem is, the composer.json doesn't specify type: drupal-module and then it gets installed in the wrong place.
That said, you could now also just skip the composer.json change entirely and then we don't have to fix that here. d.o can now set that correctly itself.
Comment #18
primsi commentedLet's see.
Comment #19
berdirWhat the test fails are saying :)
Comment #20
primsi commentedD'oh...
Comment #21
berdirI think this is ready.
Comment #22
brendanthinkshout commentedComment #24
aprice42 commentedComment #26
cjboranp commentedUsing composer for both 8.x-1.12 and 8.x-1.x gives me a "core_versions_requirement" error in mailchimp_test.info.yml which lead me here.
It seems to be shown in the branch from #22 (https://git.drupalcode.org/project/mailchimp/commit/ba865cc), but the latest version of that file does not have a core requirement:
https://git.drupalcode.org/project/mailchimp/-/blob/8.x-1.x/tests/module...
https://git.drupalcode.org/project/mailchimp/-/blob/8.x-1.12/tests/modul...
I'm just pulling the module from composer, but I downloaded the files and they also seem to be missing the core_versions_requirement line.
Comment #27
berdirI'd suggest creating a new issue. People won't look at closed issues, instead, create a new one and reference it here with a comment.
There is also a 2.x branch/release now, but looks like it has the same issue.