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

create asserts a default page width that update leaves alone

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

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
go
Área
cli

Línea de trabajo

Start with resolveWidth in cmd/create/create.go and compare its default handling with the update path described in the issue. Read the principles documentation and the export and configuration guidance mentioned here. Done means one width policy is chosen, create and update agree or the exception is explicitly documented, and the relevant behavior is reflected in the project’s guidance.

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

Descripción

create gives every new page a width of max when the file declares none. resolveWidth (cmd/create/create.go) walks --page-width, then frontmatter page_width, then the project file's page_width, and falls back to pagewidth.DefaultWidth when all three are silent. update does the opposite: an absent page_width makes no width request at all and leaves the live width alone.

That makes the two writing verbs disagree about what an absent field means, and it is the one thing keeping L9 (declared-metadata-is-asserted: a field the file declares is made true of the page; a field it omits leaves the page alone) from holding in both verbs. labels and page_status already hold in both.

The question is a decision rather than a bug fix:

  • Leave Confluence's own default. create makes no width request when nothing declares one, matching update and labels. A new page gets whatever Confluence gives a page created through the API.
  • Keep max as house style, but make it a declaration. For example, export and the docs recommend page_width: max in markfluence.yaml, and create asserts only what is declared.
  • Keep the current behavior and say in the principles doc that create asserts a default width, as an accepted exception.

Whichever it is, update and create should agree, or the difference should be written down on purpose.

Lenguaje dominante
Go
Estrellas
2
Forks
0
Merge medio
2 h 50 min
PR fusionados (30 d)
52

Guía de contribución

Abrir la guía de contribución

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 mozilla/markfluence

Todos los issues de mozilla/markfluence

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.