Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

create asserts a default page width that update leaves alone

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
go
Domain
cli

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Go
Stars
2
Forks
0
Avg merge
2h 50m
Merged PRs (30d)
52

Contributor guide

Open the contributing guide

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.

More from mozilla/markfluence

All issues in mozilla/markfluence

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.