Problem/Motivation

  • *.routing.yml files have path start with a leading slash.
  • Link field URI values referencing internal paths are stored as user-path:/... (i.e., the path portion starts with a leading slash).
  • In #2423913: Leading slash in link fields and views has different UX, we might change Views to store both paths in links and page display paths with a leading slash.
  • So, should we change the {url_alias} table to also follow the leading slash pattern?

Proposed resolution

Remaining tasks

User interface changes

API changes

Comments

xjm’s picture

xjm
she/her
Primary language English
commented
Parent issue: » #2407505: [meta] Finalize the menu links (and other user-entered paths) system
dawehner’s picture

dawehner
Primary language German
commented

I'm wondering whether we should change the API but simply drop off the "/" from the storage itself, though I guess this would be premature optimization.

dawehner’s picture

dawehner
Primary language German
commented

Kinda a duplicate of #2509300: Path alias UI allows node/1 and /node/1 as system path then fatals

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented
Related issues: +#2509300: Path alias UI allows node/1 and /node/1 as system path then fatals
dawehner’s picture

dawehner
Primary language German
commented
Status: Active » Closed (duplicate)

Let's mark it a duplicate now.