- Issue created by @longwave
- First commit to issue fork.
- ๐บ๐ธUnited States nicxvan
I'm going to do a similar naive removal here to help scope this issue and the related 3439439 ๐ Remove country setting from the installer Fixed
- ๐ซ๐ทFrance andypost
Looks having a deprecation message for 10.3 is useful here
- ๐บ๐ธUnited States nicxvan
I added a deprecated tag, I'm not sure if 10.3 is correct.
I'm also unclear if I need to do anything for:
protected $country = NULL;
and
$create_settings = [ 'langcode' => $langcode, 'country' => $this->country(), ];
- ๐บ๐ธUnited States nicxvan
Oh, I should have refreshed, it looks like andypost confirmed that 10.3 is correct, I'm not sure about the property though, I read through this:
https://www.drupal.org/about/core/policies/core-change-policies/drupal-d... โ - ๐บ๐ธUnited States nicxvan
Ok I fixed the deprecation notice and added the trigger warning.
I removed the call to country in order to get past the phpstan for now.
I think the call to the method can be removed since it's not used, but I'm not entirely sure.
I'll add the deprecated unit test shortly.
- ๐บ๐ธUnited States nicxvan
Actually I'm not sure this needs a test for deprecation since it's a protected function only called in this class. I found another example of a protected method and there are no deprecation tests for that:
https://git.drupalcode.org/project/drupal/-/merge_requests/6224/diffs#2d...
getSerializerLet me know if that is incorrect.
- ๐ฎ๐ณIndia Binoli Lalani Gujarat
Binoli Lalani โ made their first commit to this issueโs fork.
- Status changed to Needs review
9 months ago 2:54pm 9 April 2024 - Status changed to RTBC
9 months ago 3:34pm 9 April 2024 - ๐บ๐ธUnited States smustgrave
Deprecation seems straight forward. Wonder once this is merged if the ticket should just be kept open for the removal in 11.x. But lets get the deprecation merged first.
- Status changed to Fixed
9 months ago 4:03pm 9 April 2024 - ๐ฌ๐งUnited Kingdom catch
Committed/pushed to 11.x and cherry-picked to 10.3.x, thanks!
I think it's easier still to do the removal in another issue (possibly combined with other removals), another option would have been separate 11.x and 10.3.x MRs here, but both need to be reviewed and RTBCed together if so.
Automatically closed - issue fixed for 2 weeks with no activity.