Do we have a ticket for this? (not saying it’d be a quick fix, but it’d be good to have it written down if it isn’t yet)
Yes, I thought we had a ticket for years but apparently we don’t.
Just so you know but when it was allowed, seeding with POST would directly create the work.
To avoid that, because I want my user script user to review their edit before submitting, I used a fishy technique:
I left the work name blank in the POST query but then on form loading I did write the work name and hide the missing work name error with JavaScript.
This way, the form is complete with name but is not submitted right away.
2 Likes
So the Documentation creation process is
Wait till an Editor asks about a feature and then, if it exists already, tell them to write the documentation?
I suspect that improvements on that model might be found.
It is also a model that might better not be displayed to potential editors.
4 Likes
Sometimes, I’m afraid, it’s “wait until a dev remembers to document something and has time to document it at the same time”, which isn’t common. We have had cases of users speeding this with help, but I certainly wouldn’t expect them to 
I would like to think by now we are better at documenting stuff as we write it, but not all old stuff is documented properly yet 
3 Likes