Store {url_alias}.source and .alias with a leading / [#2430593]

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

Comment #1

xjm

she/her

English

commented 27 February 2015 at 00:06

Parent issue:

» #2407505: [meta] Finalize the menu links (and other user-entered paths) system

Comment #2

dawehner

German

commented 28 February 2015 at 14:52

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.