#DX (Developer Experience)

Wanted to bump 1 more time.

Left a question on the MR

The Needs Review Queue Bot → tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".

This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.

Consult the Drupal Contributor Guide → to find step-by-step guides for working with issues.

📌 TestDiscovery expects @group annotations, fails with #[Group()] attributes Active has been marked as duplicate of 📌 Deprecate TestDiscovery test file scanning, use PHPUnit API instead Active , which has been fixed. I guess this issue should be no longer postponed.

Seems like something that probably needs framework manager signoff

IMO sprintf() is clearer than string interpolation.

Ah right, I must have not seen that version. He was right anyway - t() shouldn't be used for exception messages.

Looks like some tests need to be updated.

Hey @joachim, I suspect @smustgrave was referring to using t() instead of sprintf(). Just in case he didn't mean this, i won't mark as needs work

Thank you for sharing your idea for improving Drupal.

We are working to decide if this proposal meets the Criteria for evaluating proposed changes. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or there is no community support. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

Thank you for creating this issue to improve Drupal.

We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

Thank you for creating this issue to improve Drupal.

We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

I'm pretty sure there is duplication between this issue and 🐛 Maxlength validation counts newlines twice Needs work .

Big rebase after 📌 Slowly, very slowly start OOPifying the render system Needs review .
I rewrote the CR.

Changing from a task to a bug, as evidenced by 🐛 \r\n on the config form causes the property_restrictions to not be followed Active

tim.plunkett → made their first commit to this issue’s fork.

With recipes now aren’t profiles kinda being phased out

Seems we covered only themes and modules, but what about profiles? Will a profile with the same name as the module work well?

Thanks!

LGTM.

I've filed 🐛 LazyPluginCollection::initializePlugin() doesn't document it can throw exceptions Active for the missing docs.

Why not use a single DDEV environment for a core branch and clone contrib projects into it?

Two main reasons:

• DDEV environments are cheap to spin up. It’s better to isolate contrib modules in their own environments to avoid conflicts and ensure clean, reproducible setups. Sharing a single site across unrelated modules can create unnecessary complexity around config, database, and dependency management.
• Composer isn’t great at working from local composer.json files across multiple contrib modules. It typically tries to fetch packages from the web, making it hard to test local changes to a module’s dependencies. By contrast, ddev-drupal-contrib builds directly from a module’s local composer.json, including require-dev dependencies for optional integrations.

This approach avoids local dependency tree hell and ensures all contributors run the same clean, isolated, and predictable environment.

Saving some additional credits for reviewers and maintainer triage.

Thank you for sharing your idea for improving Drupal.

We are working to decide if this proposal meets the Criteria for evaluating proposed changes. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or there is no community support. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

I ran into this recently and it cost me a debugging session. Let's get this fixed.

I used different text vs the proposed resolution, to be consistent with the verbiage for the related filterByFieldAccess method.

john.oltman → made their first commit to this issue’s fork.

Looks great @salvatoren, thanks for confirming!

Hopefully, since Forum is now a contrib module, this great update can get committed before too long. It would be epic to land this 12 year old issue, way back from June 2013 :)

A couple comments on the MR.
CR also needs a version bump.

Wanted to give this one 1 more bump.

🐛 Canonical taxonomy term link for forum vocabulary is broken Postponed reminded me of this; forum is removing use of uri_callback, once comment does as well then it can be removed from core entirely.

Rebased the MR, updated the deprecation for 11.3, updated issue credit, I think this is ready to go.

Removed these from the IS as they already exist as followups:

📌 Rename Comment::permalink() to not be ambiguous with ::uri() Needs work
📌 Deprecate uri_callback in routes for entities Needs work

Hi, i too applied the patch: 2010132-154.patch - and add this two pathauto field:

Seems to work as expected now :)