Non-coders don't know which properties a given field has.
There are lots of issues that are essentially support requests for this.
(Todo: Postpone them all on this issue.)
Provide the field properties info in the help text of our settings.
tbd
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | Screenshot from 2025-10-15 10-10-43.png | 76.75 KB | vitaliyb98 |
| #5 | Screenshot from 2025-10-14 15-33-03.png | 94.95 KB | vitaliyb98 |
Show commandsStart within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #2
ressaThanks for showing understanding to non-coders :)
As a quick win, the first line in the project page description could also be updated to cover both coders and non-coders?
"Prepopulate any node or term field (or any entity) with Token values."
Personally, I would always search for "node token prefill" or something like that, I have never searched for the word "entity", like most non-coders as well.
Comment #5
vitaliyb98 commentedAs a start, I added a draft functional which shows all available properties for the current field
Need to discuss the next thing:
- Maybe there is a better form to describe property, currently used in such a format:
<b>@label</b> — machine name: <i>@machine_name</i> (type: @type)Example: Summary — machine name: summary (type: string)- Currently, all available properties of the field are displayed, even if some of them will never be used for prepopulating.
Comment #6
geek-merlinLooks like a good start! Natural next steps (and imho all we need here) are:
- Change the list format to sth like this (the machine name is the main interesting thing, so comes first):
- format: Text format - Add description here if there is one.
- Filter out irrelevant properties: isInternal(), isReadOnly(), isComputed() (which here kicks out the processed-properties).
Comment #7
vitaliyb98 commented@geek-merlin, I made a change according to your comment, looks better:
Comment #8
geek-merlinSo then it's good to go!
Comment #10
vitaliyb98 commentedMerged into 8.x-1.x