Problem/Motivation
Modernize the code and support Drupal 9.5 and 10.0.
This issue takes https://www.drupal.org/project/views_linkarea/issues/3290506 and makes next steps more clear.
Proposed Resolution
* Create 2.0.x (semantic versioning) branch
* Set default testing for 2.0.x branch
* Ensure tests pass for Drupal 9.5 and 10.1 for the 2.0.x branch -- these currently fail
* Create 2.0.0 release
* Set 2.0.x as default branch
I would not release 8.x-1.5 because we should not support Drupal 8.9.
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | 3332783-views_linkarea-phpstan-9.patch | 6.24 KB | agentrickard |
| #8 | 3332783-views_linkarea-phpstan-8.patch | 1.33 KB | agentrickard |
| #3 | 3332783-views_linkarea-phpstan.patch | 554 bytes | agentrickard |
Comments
Comment #2
agentrickardSee the branch tests at https://www.drupal.org/node/772628/qa
Comment #3
agentrickardPHP Stan also has errors to report:
Here's a simple patch to trigger the testbot for this issue.
Comment #4
anybodyWe'll have a look here, thanks @agentrickard. Can we use a MR for that, based on your patch? I think that would make things easier.
I'll ask my teammate @Grevil to help, as I'm very busy this week.
Comment #5
anybodyCould this be the reason for the failing tests?
#3056234: User context missing when using toUrl in some circumstances
I was searching for the error message.
Comment #6
agentrickardRegarding releases: In general, I have been keeping an 8.x release if we feel that people are still running Drupal 8 (which they shouldn't), so we could remove Drupal 10 support from 8.x-1.x, tag a stable 8.x-1.6 for Drupal 8 || 9, and then release 2.0.0.
We would mark 2.0.0 as the "supported" version. See https://www.drupal.org/project/workbench_access for an example of this pattern.
First, I'd like to get this test to pass. The phpstan issues can be addressed later.
Comment #7
agentrickardMR is fine -- I still use a patch workflow on d.o., but if you prefer MR, go for it.
And yes, that looks like the test error.
Comment #8
agentrickardIndeed, that issue had the answer. Apparently Kernel tests don't create any users, and the anon user is required for the access context.
Comment #9
agentrickardThis should be fine for a release. I marked a number of items as
@phpstan-ignore-next-linerelated to strick checking of theempty()check. I am not sure what syntax is better in those cases.I think those can be cleaned up in a follow-up issue.
Comment #10
agentrickardThis has been committed.
Comment #11
anybodyNice!!
Yes indeed! Once @Grevil has a bit more spare time than me, he'll surely also have a look at the tests and code style issues. Feel free to add him as Co-Maintainer.
Comment #12
agentrickard@Anybody -- I went ahead and updated the releases, added @Grevill and boosted your maintainer privileges, too.
I also set 2.0.x to be the default branch and set default testing to Drupal 10.1 and 9.5
Comment #13
grevil commentedThank you, @agentrickard!
I see you already fixed the tests! I am not too seasoned with Kernel Tests, but they LGTM! We can surely add a few more tests in the future, but for now I think they are fine!
Comment #14
grevil commentedI created a follow-up issue for the remaining problems here: #3334757: Code style and phpstan fixes..
Comment #15
agentrickardCool. I'm going to back away from this module now.