I noticed in all of my capture templates (which are mostly entry type) that the id is now created on the first headline, rather than at the top of the file. (Seems to be this pull request.) I don’t have a strong opinion about this either way, but was just curious what this change is designed to achieve? I’ve been thinking in “very small files, each with an id” and this change makes me think maybe I should have bigger files and ids on headings. Is that the idea?
I think people “expect” entries to have IDs. I personally think it was trivial to achieve this even before - during capture just call the org-id related function and so on. The capture process is incredibly cumbersome for something simple it does and as one can see automating this minor change requires such a big patch.
I think you should organise your files as you see fit. Don’t update if you want the older behaviour or just reverse patch that particular one and carry on with life 
In the most frustrating case - users have to move to org-capture instead of org-roam-capture for entries.
Having minimal number of ids in a file is the “correct’“ approach to maintaining notes for me. I use entries to just create a heading and nothing else.
1 Like
P.s. hopefully no more annoying errors like this
Probably for the best that entries now get id straight away. But yea - unless you need to capture and insert 2nd or below levels immediately - and you don’t want to have IDs for every entry - you can safely undo the patch if you find the previous behaviour better.
But I think this change will prevent annoying bugs like these in the future for everybody else (hopefully)
Thank you. Seeing the kind of issue it was addressing makes it clearer. I’m fine with the change, so I’ll just stay kept up with the main branch. (I use straight.el, which is probably why I spotted this early.) As I said, I don’t have any strong opinions, and this change makes the top of my files a bit cleaner, so… all good!
Thanks for the wonderful work! I literally live in org and org-roam.