Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
taxonomy.module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
21 Dec 2014 at 06:25 UTC
Updated:
27 Jan 2015 at 13:24 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
hussainwebComment #2
mile23Good work on plowing through these issues.
Changing the array declarations is really out of scope, but not that big a deal.
You added $vocabulary to both TaxonomyTestBase and VocabularyUiTest, which is its subclass. I'd leave the one in TaxonomyTestBase and remove the one in VocabularyUiTest.
Comment #3
hussainwebResponding to comments in #2:
1. I know it is out of scope but I am touching all that I can. It looks concise and much better. Of course, there is no difference in functionality.
2.
VocabularyUiTestextends\Drupal\taxonomy\Tests\TaxonomyTestBase. The other$vocabularydefinition is actually in\Drupal\taxonomy\Tests\Views\TaxonomyTestBase. They are different classes. This means we need to define$vocabularyinVocabularyUiTestas well.I am setting it back to needs review as there is nothing to do here. :)
Comment #4
mile23OK, so checking with phpcs I find that the error of having under_score property names is fixed to camelCase. The $variables question is answered, and yes, you're right, they're different. The out-of-scope change isn't such a big deal, so RTBC the patch in #1.
Comment #5
alexpottThese are out-of-scope changes.
Comment #6
hussainwebThere is no interdiff as this was also a reroll. I removed all the changes with the new array syntax except where the lines are very different.
Comment #7
mile23Thanks for sticking with it, @hussainweb. :-)
Patch in #6 fixes the camelCase errors, and also doesn't have out of scope array definition changes.
Comment #8
alexpottCommitted a658710 and pushed to 8.0.x. Thanks!
Thanks for adding the beta evaluation to the issue summary.