fix: usage of contentSourceEditPattern

[mhaack]

Description

A configured custom edit url should always be used first.

Related Issue

fix: #803

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[mhaack]

@rofe @auniverseaway please have a look, we introduced editUrlLabel and editUrlPattern with #245 back the the page status did not return and edit URL for BYOM I remember. But now, at least for DA, it does return an edit URL, hence to config does not work any more.

[rofe]

@mhaack can you add a test clarifying the intended behavior?

[rofe]

for DA, it does return an edit URL, hence to config does not work any more.

that change was intentional: the assumption was that if an edit URL is provided by the backend, it should supercede the config pattern.

[mhaack]

that change was intentional: the assumption was that if an edit URL is provided by the backend, it should supercede the config pattern.

Ok my change would do the opposite. Customers (DA) want to overwrite the edit URL provided by the backend, for example to open UE directly instead of the doc based editor.

[mhaack]

@rofe added as test as well

[github-actions]

🎉 This PR is included in version 7.28.2 🎉

The release is available on:

• GitHub release
• v7.28.2

Your semantic-release bot 📦🚀