NotePlan / NotePlan/plugins

Updating File Names based on Note Titles

Open
#457 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
204
Forks
82
Avg merge
22h 27m
Merged PRs (30d)
3

Description

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!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by locating the plugin entry points that create or rename note files, then review how titles and naming collisions are handled. Before implementation, clarify whether the goal is automatic renaming, a batch command, or both, along with the workspace scope and collision behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.