Using stdin as report input could be cool if the report is stored (and even versioned) in DB and depending on the date you need to pick a concrete version. Since we're talking about finite number of reports, it can be also saved to disk (on startup)...
Having reports only as links is a trade-off I could live with. Although in lot of cases life is easier when important data are in the DB (only one place to back up).
And to your question: yes, I'll create that ticket (). I'd like you to ask to give a higher priority for this one, if possible. Also call in friends, we need votes
It is not so much about voting, it is more about my limited time
Every useful feature should be implemented once.
The possibility to exactly reproduce a historical report, even with original layout, can be a requirement in some cases.
Using stdin for the report source may have some limitations but also a usecase. Feel free to create an additional issue for it too.
Would be nice if some of your friends are programmers
We too would love to see this feature, along with for much the same reasons as discussed (we also like the security aspect of not needing the temporary files littered around). Though we are also interested in the versioning of the report, we address that using git's worktree capability and so using stdin for that is less interesting.
I've just updated the PR to include appropriate testing. Please review/consider for inclusion.