NotePlan / NotePlan/plugins

Updating File Names based on Note Titles

Abierto
#457 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Lenguaje dominante
JavaScript
Estrellas
204
Forks
82
Merge medio
22 h 27 min
PR fusionados (30 d)
3

Descripción

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!

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Línea de trabajo

No se especifican archivos, pruebas ni puntos de entrada. Empieza por localizar los puntos de entrada del plugin que crean o renombran archivos de notas y, después, revisa cómo se gestionan los títulos y las colisiones de nombres. Antes de la implementación, aclara si el objetivo es el renombrado automático, un comando por lotes o ambos, además del alcance del workspace y el comportamiento ante colisiones.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
javascript
Área
desktop
Tipo de issue
Nueva funcionalidad
Dificultad
5/5
Tiempo estimado
Más de una semana
Estado de actividad
Estancado
Claridad
Necesita aclaración
Aptitud para principiantes
25/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.