Updating File Names based on Note Titles
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- JavaScript
- Sterne
- 204
- Forks
- 82
- Ø Merge
- 22 Std. 27 Min.
- Gemergte PRs (30 T.)
- 3
Beschreibung
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Not a problem, per se, but I occasionally look at the contents of my NotePlan directories and I notice that even though note files get their initial names from their note titles, most of the time the filename does not match the current title. This happens mostly because files don't get renamed when the note title changes. I expect it's made worse if you frequently use templates that have boilerplate titles.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Depending on complexity and reliability, it would be nice if we could choose via setting/preference to have our note filenames change every time the title does. Otherwise, it would be nice to have a command that would help us batch update all of our filenames based on the titles of each note. Either within the current folder, or entire workspace.
In the event of a naming collision, whereby two notes in the same directory have the same note title, the current approach would be fine, i.e. appending a number to the end of the filename to make it unique, although I think it would be the bees knees if instead of the next sequential number, the filename was appended with maybe the current timestamp?
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
Very brief discussion from Discord here. Thanks for your consideration, I appreciate the team very much!
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Es werden keine Dateien, Tests oder Einstiegspunkte genannt. Beginne damit, die Plugin-Einstiegspunkte zu finden, die Notizdateien erstellen oder umbenennen, und prüfe anschließend, wie Titel und Namenskollisionen behandelt werden. Kläre vor der Implementierung, ob das Ziel die automatische Umbenennung, ein Batch-Befehl oder beides ist, sowie den Geltungsbereich des Workspace und das Verhalten bei Kollisionen.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- javascript
- Bereich
- desktop
- Issue-Typ
- Feature
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 25/100