Open ZeroKun265 opened 2 months ago
Why does the date being when the article file was last modified make it a problem if you have to reexport. If you modify a note then that note should be shown newer than one that was created or modified before it. It doesn't seem to make sense to me that reexporting should change the RSS. I can consider adding a property for this but I really want to reduce complexity of the plugin since it is already a huge beast of code lol.
Why do you want a custom date instead of just using the date when the note was modified? I am not sure I understand your reason for this
Thanks!
My reasoning is I'm building a sort of blog using the plugin and so I have some old articles I wrote a while back, but of course the date now shows as much more recent. Also, since I'm still building it I constantly make changes to the layout of the articles, or even just grammar fixes, so then the date is no longer the correct date of writing
I 100% understand if you don't want to add the feature. I'd honestly add it myself if I understood anything about plugin development
I will definetly consider adding this, it could be useful. I have also just organized the rss settings so it shouldn't add too much clutter.
Is your feature request related to a problem? Please describe. I'm trying to use this to make a kind of blog, i know it's not really the correct use case but it's a bit of an experiment Right now the date depends on when the article file was created, which becomes a problem if you have to reexport (let's say to add a fix to it)
Describe the solution you'd like An option in the settings to override the pubDate, like we have one for the title of a note the time can be a default value, or the time of exporting (or the date and time property could be used)
Describe alternatives you've considered I don't think there are really any alternatives to this
Additional context None