Closed ccjjmartin closed 2 years ago
This might be more involved than updating this line. At the very least, anything in /templates
should be updated to match the corresponding folder structure and file contents in Stable9's theme, but we should also test to ensure it is compatible and doesn't have errors.
I updated the description to include the templates I thought needed to be review as part of this PR.
Looking over the blocks but not making changes yet I have the following comments:
block.html.twig
file I noticed that we replaced {{ attributes }}
with {{ bem() }}
I know at one point we had attributes working with in Emulsify. Would it not be better to print both the full attributes object without classes and then print classes coming from Drupal with our bem classes tacked on to the end of the list? Then we get even more integration with the Drupal backend?node.html.twig
same as above otherwise looks like nothing changedpage-title.html.twig
same as above, we are removing the ability for the backend to render title attributestable.html.twig
interestingly enough here we are adding the class table to the attributes object and not using bem at all. {{ attributes.addClass('table') }}
Otherwise, other differences were that we added some bem classes (hard coded) to the table rows but everything else from core is already there.checkboxes.html.twig
- Looks like we have a todo on this to remove some files related to this when a drupal core issue is resolved but it is still marked as active: https://www.drupal.org/node/1819284field-multiple-value-form.html.twig
- same as above form commentfieldset.html.twig
- looks like we added form-fieldset
class, we are missing a possible new class "fieldset-legend", we are also missing a span within the legend that has some attributes around the titleform-element-label.html.twig
- good to go here, no changes neededform-element.html.twig
- missing some new classes coming from core, needs workinput.html.twig
- good to go here, no changes neededradios.html.twig
- good to go here, no changes needed (unless we want to fix the bem class being added form-item--radio
this isn't consistent across form items, example form-item__textfield
select.html.twig
- we added an extra wrapping div or it went away, {% apply spaceless %}
versus what we have {% spaceless %}
textarea.html.twig
- good to go here, no changes neededpage.html.twig
- we aren't consistent with core at all so I am going to skip reviewing thisstatus-messages.html.twig
- missing a data attribute, aria label needs, some changes, basically this one needs some workbreadcrumb.html.twig
- looks good, no changes necessarymenu-local-action.html.twig
- wipes out the attributesmenu-local-task.html.twig
- not comparable to what Drupal has, we rewrote the tabs component completelymenu-local.tasks.html.twig
- not comparable to what Drupal has, we rewrote the tabs component completelymenu.html.twig
- not comparable to what Drupal has, we rewrote the tabs component completelypager.html.twig
- needs further review but looks very similarviews-view-unformatted--frontpage.html.twig
- not comparable@ccjjmartin Has this been completed? I thought we did something to update the files... Maybe I'm wrong?
@ModulesUnraveled Yep, here is the PR: https://github.com/emulsify-ds/emulsify-drupal/pull/210
Guess I didn't close the issue associated with it. Closing.
Need to update documentation and this line to reflect stable9 instead of stable. Sous also needs to be updated to enable the stable9 theme as you get a fatal error by depending upon it but not enabling it.
Review the templates directory I found that we don't have a lot of templates that stable9/stable do, for purposes of scoping this issue I am going to leave out all of the templates that we don't currently have and only focus on reviewing the ones that we do have and are included in stable9:
List of components to be included in this issue: