Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Inconsistent "New note" name behavior in web UI

Abierto
  • ¿Algo no está bien?
#1,653 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
45/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
javascript
Área
frontend

Línea de trabajo

Comienza reproduciendo la secuencia de creación y guardado de notas en la interfaz web y, a continuación, sigue el código que gestiona los títulos de las notas durante su creación y guardado. El fix está terminado cuando las notas creadas como “New note” reciben nombres coherentes y las ediciones posteriores siguen un comportamiento de nomenclatura coherente en toda la secuencia descrita.

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

Descripción

bug need to reproduce

This is a very minor bug.

Steps to reproduce

  1. Ensure no notes are named "New note"
  2. Create a new note in the web UI (I will call this note A)
  3. Observe the note is named "New note"
  4. Write "foo" in the note body
  5. Click on the check icon to save the note
  6. Observe the note is renamed to "foo"
  7. Edit "foo" in the note body to "foobar"
  8. Click on the check icon to save the note
  9. Observe the note is renamed to "foobar"
  10. Create a new note in the web UI (I will call this note B)
  11. Observe the note is named "New note"
  12. Write "bar" in the note body
  13. Create a new note in the web UI (I will call this note C)
  14. Observe note B is still named "New note"
  15. Observe note C is named "New note (1)"
  16. Write "baz" in the note body
  17. Create a new note in the web UI (I will call this note D)
  18. Observe note B is still named "New note"
  19. Observe note C is named "New note (1)"
  20. Observe note D is named "New note (2)"
  21. Write "quux" in the note body
  22. Click on the check icon to save note D
  23. Observe note D is renamed to "quux"
  24. Click on note B
  25. Edit "bar" in the note body to "bar bar"
  26. Click on the check icon to save note B
  27. Observe note B is renamed to "bar bar"
  28. Edit "bar bar" in the note body to "bar bar bar"
  29. Click on the check icon to save note B
  30. Observe note B is renamed to "bar bar bar"
  31. Click on note C
  32. Write "baz baz" in the note body
  33. Click on the check icon to save note C
  34. Observe note C is still named "New note (1)"
  35. Click on note B
  36. Edit "bar bar bar" in the note body to "bar bar bar bar"
  37. Click on the check icon to save note B
  38. Observe note B is still named "bar bar bar"
  39. Question my sanity after writing this
Expected behaviour

Consistent

Actual behaviour

Inconsistent

Server

  • Notes app version: 4.12.3
  • Nextcloud version: 32.0.0.13
  • OS: Debian 12.11
  • Web server: apache2 2.4.62
  • PHP version: 8.2.28
  • Database: MariaDB 10.11.11

Nextcloud configuration:

"system": {
    "instanceid": "***REMOVED SENSITIVE VALUE***",
    "passwordsalt": "***REMOVED SENSITIVE VALUE***",
    "secret": "***REMOVED SENSITIVE VALUE***",
    "trusted_domains": [
        "nextcloud.example.com"
    ],
    "datadirectory": "***REMOVED SENSITIVE VALUE***",
    "dbtype": "mysql",
    "version": "32.0.0.13",
    "overwrite.cli.url": "https:\/\/nextcloud.example.com",
    "dbname": "***REMOVED SENSITIVE VALUE***",
    "dbhost": "***REMOVED SENSITIVE VALUE***",
    "dbport": "",
    "dbtableprefix": "oc_",
    "mysql.utf8mb4": true,
    "dbuser": "***REMOVED SENSITIVE VALUE***",
    "dbpassword": "***REMOVED SENSITIVE VALUE***",
    "installed": true,
    "memcache.local": "\\OC\\Memcache\\APCu",
    "memcache.distributed": "\\OC\\Memcache\\Redis",
    "redis": {
        "host": "***REMOVED SENSITIVE VALUE***",
        "port": 0,
        "dbindex": 0,
        "password": "***REMOVED SENSITIVE VALUE***",
        "timeout": 1.5
    },
    "maintenance": false,
    "maintenance_window_start": 1,
    "theme": "",
    "loglevel": 2,
    "default_phone_region": "US",
    "mail_smtpmode": "smtp",
    "mail_smtpsecure": "ssl",
    "mail_sendmailmode": "smtp",
    "memories.exiftool": "\/var\/www\/nextcloud.example.com\/apps\/memories\/bin-ext\/exiftool-amd64-glibc",
    "memories.vod.path": "\/var\/www\/nextcloud.example.com\/apps\/memories\/bin-ext\/go-vod-amd64",
    "memories.db.triggers.fcu": true
}

}

Client

Please complete the following information.

  • Browser (incl. version): Firefox 142.0 (64-bit)
  • OS: Debian forky/sid (using KDE)
Lenguaje dominante
JavaScript
Estrellas
738
Forks
162
Merge medio
2 h 32 min
PR fusionados (30 d)
41

Preparar el entorno

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.

Más de nextcloud/notes

Todos los issues de nextcloud/notes

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.