Comments

temoor’s picture

Status: Active » Needs review
StatusFileSize
new2.37 KB
Michael Hodge Jr’s picture

Status: Needs review » Reviewed & tested by the community

I've applied the patch, grepped the code, and can confirm everything looks ok.

Michael Hodge Jr’s picture

Status: Needs review » Reviewed & tested by the community

I've applied the patch, grepped the code, and can confirm everything looks ok.

alexpott’s picture

Status: Reviewed & tested by the community » Needs work

This should be postponed on #2271529: Move breakpoint settings to theme and module *.breakpoints.yml files at root level and also this should be injecting the storage into the plugin.

temoor’s picture

Status: Needs work » Needs review
StatusFileSize
new3.92 KB
new3.95 KB

Added changes according to #4

roderik’s picture

Issue tags: +Amsterdam2014

Tagging for Amsterdam. This is for an experienced PHP coder but novice contributor. While reviewing / checking if this patch still covers all existing calls in Core, you will learn about Drupal's dependency injection with a practical example (which is this patch). If you set this is RTBC, feel free to comment about how and why you came to the conclusion.

oenie’s picture

I'm checking it out, rerolling it because it doesn't apply anymore.

jepster_’s picture

Hi there,

oenie was so nice to reroll the patch with me and show me a lot of interessting git patching workflow things by the way. :)

Thanks

jepster_’s picture

We've found one occurence of entity_load(); and replaced it.

New patch attached.

oenie’s picture

Jepster, it seems it accidentally also registered the changes our Backend-Developer (service :)) made to you .gitignore file.
I've removed the lines and uploaded the (hopefully final) new patch, along with an interdiff (as requested by that same BDS :))

Status: Needs review » Needs work

roderik’s picture

Status: Needs work » Needs review

Looks good to me on patch review: storage is properly injected, no calls left.

roderik’s picture

Status: Needs review » Reviewed & tested by the community

...and this should actually have been 'needs review' already (re-queued patch passed), so RTBC

alexpott’s picture

Status: Reviewed & tested by the community » Needs work

Looking really good... one small thing:

+++ b/core/modules/responsive_image/src/Plugin/Field/FieldFormatter/ResponsiveImageFormatter.php
@@ -23,7 +27,37 @@
+  /**
+   * {@inheritdoc}
+   */
+  public function __construct($plugin_id, $plugin_definition, FieldDefinitionInterface $field_definition, array $settings, $label, $view_mode, array $third_party_settings, EntityStorageInterface $responsive_image_mapping_storage) {

Unfortunately you can not inheritdoc here because you are adding an argument - $responsive_image_mapping_storage.

oenie’s picture

Added the missing docblock.

oenie’s picture

Status: Needs work » Needs review

Added the missing docblock.

oenie’s picture

Safely ignore this double post

roderik’s picture

Status: Needs review » Needs work

Thanks. Setting back with one nit pick...

+++ b/core/modules/responsive_image/src/Plugin/Field/FieldFormatter/ResponsiveImageFormatter.php
@@ -35,7 +35,24 @@ class ResponsiveImageFormatter extends ImageFormatterBase implements ContainerFa
+   *   Any third party settings settings.

Language glitch (double 'settings'). This glitch is also in the FormatterBase doc block (can be fixed there too?) so I get how that was copied...

rpayanm’s picture

Status: Needs work » Needs review
StatusFileSize
new7.88 KB
new2.85 KB

I found two more :)

roderik’s picture

Status: Needs review » Reviewed & tested by the community

Cool.

I'm guessing that these extra one-line documentation changes do not cross the "this should be a separate patch" border...

  • alexpott committed fa1d2c3 on 8.0.x
    Issue #2322037 by oenie, Temoor, jepSter, rpayanm: Replace all instances...
alexpott’s picture

Status: Reviewed & tested by the community » Fixed

@roderik these extra one-line documentation changes should have gone in another patch but let's not hold up this patch on that. The things is we're changing code completely out of context to the issue and risk causing rerolls in unrelated patches. However I think that the reroll risk is very small. So...

Committed fa1d2c3 and pushed to 8.0.x. Thanks!

Status: Fixed » Closed (fixed)

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