Exclusion patterns to give users more control

Created on 12 June 2024, 4 months ago

Excellent module, but I would like more control over what gets the alias and what doesn't.

I propose new form options to allow users to set exclusions that override the main regex match.

  • Excluded regex field - anything that matches is skipped.
  • Route Options field - use route options, such as '_admin_route' to exclude any routes with that option. Providing a default option (_ignore_path_alias_xt) that gets ignored would be helpful to standardise for developers.

My use case is that I like the /node/{node}/edit path, as it is the quickest way to find the node id. Trying to add exclusions using the current form would be difficult and soon get out of hand if you had multiple rules.

Feature request
Status

Active

Version

2.0

Component

Code

Created by

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @scambler
  • Attached is the proposed patch.
    Whilst creating this issue I had the idea of creating a route option '_ignore_path_alias_xt' to give developers an easy way to avoid the aliasing. This is a pretty niche situation, so I will leave it to the maintainers to decide whether it's worth adding that to the default config.

Production build 0.71.5 2024