Skip to content

Conversation

@tibi2303
Copy link
Collaborator

No description provided.

@github-actions
Copy link

🚀 Deployed on https://preview-710--oelibrary.netlify.app

@github-actions github-actions bot temporarily deployed to pull request November 12, 2025 14:38 Inactive
{% macro render(items, pills, tabs, tabs_content, vertical, full_width, alignment, id, nav, navbar, attributes) %}
{% apply spaceless %}
{% import _self as navigation %}
{% import _self as navigation %}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think identation is wrong.


const escapeRegExp = (value) => value.replace(/[.*+?^${}()|[\]\\]/g, "\\$&");
let start = 0;
let seenLineBreak = false;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the removals of the spaceless is ok, Drupal core has done this, Im wondering if we should remove spaces from the tests. This is altering the real output, drupal-attribute is ok since will be the expected result when templates go through Drupal, but not sure if spaces/break lines are removed, so this is not what the HTML will be.

Do we want to remove the trim of extra spaces and break lines? If we remove spaceless and tests start to fail that tells me that we are not replacing the functionality. Do we want to keep it as it was?

I've seen we use - or ~to remove extra spaces in some templates, assuming we keep the same functinality maybe we can work around that but may not fit in all scenarios.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants