Support from Acquia helps fund testing for Drupal Acquia logo

Comments

maryedith created an issue. See original summary.

maryedith’s picture

sorabh.v6’s picture

Assigned: maryedith » sorabh.v6
sorabh.v6’s picture

Assigned: sorabh.v6 » Unassigned
Status: Needs review » Needs work

Hey @maryedith, I reviewed patch file. Below are some findings that should be corrected -

  1. +++ b/core/modules/language/language.module
    @@ -270,6 +270,8 @@ function language_get_default_langcode($entity_type, $bundle) {
    + * @see https://www.drupal.org/node/2182661
    

    @see should be mentioned after @deprecated.

  2. +++ b/core/modules/language/language.module
    @@ -299,6 +301,8 @@ function language_negotiation_url_prefixes_update() {
    + * @see https://www.drupal.org/node/2182661
    

    @see should be mentioned after @deprecated.

Thanks for the patch file.

Dinesh18’s picture

Assigned: Unassigned » Dinesh18
Dinesh18’s picture

Status: Needs work » Needs review
FileSize
1.01 KB

Here is the updated patch which incorporates the #4 comments.

Dinesh18’s picture

Assigned: Dinesh18 » Unassigned
sorabh.v6’s picture

Status: Needs review » Needs work

Hey @Dinesh18, Everything's good with your patch. Only has a trailing whitespace on line 9 which needs to be taken care of. Please remove it.

Thanks for your work. :)

dhruveshdtripathi’s picture

Changes made according to comment #8

Thank you!

dhruveshdtripathi’s picture

Status: Needs work » Needs review
Dinesh18’s picture

Status: Needs review » Reviewed & tested by the community

Applied the patch mentioned in #9. Resolved the trailing whitespace error.
Changing the status to RTBC.

Gábor Hojtsy’s picture

Status: Reviewed & tested by the community » Needs work

https://www.drupal.org/node/2182661 is certainly not related to the patch that added these depreciation notices. Which patch added the depreciation notices? Does it have a change record?

Mile23’s picture

language_negotiation_url_domains() and language_negotiation_url_prefixes() were deprecated in #2403229: language.negotiation configuration can have overrides bleed in which does not have a change record, though it does have an API change. However, @alexpott mentions that a CR isn't needed: #2403229-34: language.negotiation configuration can have overrides bleed in

That issue has two follow-ups that aren't finished: #2462729: Move ConfigurableLanguage hook implementations in language module to the entity #2548079: Move language negotiation prefix logic update to ConfigurableLanguage

Gábor Hojtsy’s picture

In that case I think we need to add that change record so we can link to it and people find out what it is. We could like to the issue as well theoretically but we don'd do that in these links because change records are much easier to parse and act on.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

billywardrop’s picture

I'm at DrupalCon vienna and I'll pick up this issue.

billywardrop’s picture

The change for the functions language_negotiation_url_prefixes() and language_negotiation_url_domains() happened in #2403229-31: language.negotiation configuration can have overrides bleed in and no change record was created. I'll draft a change record for this.

billywardrop’s picture

sorry misposted

billywardrop’s picture

I have created a patch to link to the new change record https://www.drupal.org/node/2912748 for the functions language_negotiation_url_prefixes() and language_negotiation_url_domains()

billywardrop’s picture

Status: Needs work » Needs review
tedbow’s picture

Title: Add Change record to @deprecated for language.module » Add Change record to @deprecated for Domain::Config Language Negotations
Issue summary: View changes
Status: Needs review » Reviewed & tested by the community

Thanks for everyone for work on this!

I am changing the title for this issue because as per #2873705: Add change records to all @deprecated code we need scope these types of issues by change records not by files. Please read that more issue for the complete instructions.

Luckily though both the changes in this patch do link to the same change record: https://www.drupal.org/node/2912748 (@billywardrop thanks for finding the correct one!)

Looking back at the issue related to this change record #2403229: language.negotiation configuration can have overrides bleed in and the commit for this issue http://cgit.drupalcode.org/drupal/commit/?id=52e5d45 the 2 @deprectated tags covered by this patch are the only ones added by this commit.

If there were more @deprecated tags added by this change we would want to include them in this patch even if they were not in language.module file(hence the name change). This is important because it gives reviewers and committers the confidence that we have search for @deprecated instances from this change(so they don't get forgotten).

This looks good to me!

I have also applied the patch and confirmed that there are no trailing spaces any more as mentioned by @dhruveshdtripathi in #9

  • xjm committed b4291de on 8.5.x
    Issue #2874700 by dhruveshdtripathi, billywardrop, Dinesh18, maryedith,...
xjm’s picture

Version: 8.5.x-dev » 8.4.x-dev

That looks good to me, thanks!

Committed to 8.5.x. As a documentation improvement, this issue can be backported, but leaving RTBC against 8.4.x since we're in commit freeze for 8.4.1 at the moment. We'll cherry-pick the commit after the freeze.

Status: Reviewed & tested by the community » Needs work

The last submitted patch, 19: add_change_record_to-2874700-19.patch, failed testing. View results

billywardrop’s picture

It says that this patch still needs work but is already commited? What work still needs to be done to this ticket to complete it?

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

quietone’s picture

Status: Needs work » Fixed

This was commited 4 years ago, changing to fixed.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.