Add support for permalink

[ctmbl]

Create an endpoint in the backend for each note (for example /note/<UUID>) as alias of the natural endpoint /note/<note title>, but that doesn't change when the note is renamed.
It would automatically redirects to the natural URL and would be removed when the note is deleted.

[dullage]

The trouble with this is that it would require a way to store the mapping, which would need to be maintained whenever a file is renamed.

Currently, flatnotes is essentially stateless (apart from the note files) and it allows notes to be edited/deleted/renamed outside of flatnotes. Both are approaches I'd like to keep.

[ctmbl]

@dullage
Thanks for the quick answer!
I totally get your point, and agree with you that flatnotes being stateless is one of its strength.

However, if you're interested in the feature (now or in the future), you could store this information inside the notes themselves (keeping flatnotes database-less), as you already do with tags.
The HUGO framework (maybe you're already familiar with) do this with a front matter, a yml/toml/json section at the beginning of the .md file. You'll find an example here.
But this is of course just an example on how to achieve this!

I say this as a suggestion of course, so feel free to let this issue closed if not that much interested in the feature 🙂

[dullage]

For the front matter concept to work, I couldn't open each file to find the one being requested, so I'd need to keep a log of which files contained which UUIDs. At this point, unfortunately, we're back to needing a database. Now, I could keep track of this in the search index, but then essentially I'd be using the index as a database (something I already do to some degree, but it feels like a slippery slope to fall down).

I'm happy to leave this open as a suggestion to record interest, but I don't think it's something likely to be tackled in the short-term.