Reserved field names

[Gitsack]

Hi there. :)

Since I stumbled over this once again today in a repository, I got an idea about how this could be avoided:

Issue

There are a couple of "reserved" names which interfere with standard Statamic behavior. For example, when creating a text field for a URL and giving id a handle of "link", this can result in unwanted things that sometimes take some time to debug - in this case:

{{ link :id="id" }}

results in an error since the id modifier is not present on a string because the field might overwrite the built in link tag.

Idea

In my opinion, it would be a huge help to use the list of reserved words that already exists which might be additionally auto-populated by adding all built-in tag handles etc. for an internal check list. This list could then be used when naming a field to quickly check if this would conflict with some Statamic internal name. If there was a warning somewhere on or below the field, this would be a great quality of life improvement, and would maybe make sense there directly in the UI.

--

What do you think? And would there be a sensible place for this maybe in the revamped v6 interface? :)🖖