This is a stable blocker for SDC.

We're fairly confident that automated tests, as Drupal's implementation of Twig already covers this, however we want to be đź’Żđź’Żđź’Ż sure.

If needed, tests need to be created. If not needed, we will document why not.

Comments

mherchel created an issue. See original summary.

e0ipso’s picture

e0ipso
Primary language Catalan
Location Can Picafort
commented

This comment contains proof of manual testing for this. Let's keep discussing whether we need automated tests for this.

rohan-sinha’s picture

rohan-sinha commented

i think there are 2 ways,
To keep people actively testing we can add a checklist for manual test to validate SDC
OR
To use the technologies and independent from the human mistakes, we can use automation testing.

e0ipso’s picture

e0ipso
Primary language Catalan
Location Can Picafort
commented

I am leaning towards closing this as a won't fix. Maybe @lauriii can comment on this since he raised the concern.

My reasoning is that we are not doing anything to escape sandbox and escaping (no pun intended), and therefore the existing sandbox and escaping tests have our backs on this one.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

e0ipso’s picture

e0ipso
Primary language Catalan
Location Can Picafort
commented
Status: Active » Closed (won't fix)

Closing.