Skip to content

Fix generated block size docs.#10482

Merged
jmcarp merged 1 commit into
mainfrom
jmcarp/block-size-docs
Jun 4, 2026
Merged

Fix generated block size docs.#10482
jmcarp merged 1 commit into
mainfrom
jmcarp/block-size-docs

Conversation

@jmcarp
Copy link
Copy Markdown
Contributor

@jmcarp jmcarp commented May 22, 2026

Represent Disk::block_size as a BlockSize rather than a ByteCount, so that the generated spec and docs are correct. This is technically a breaking change, even though both BlockSize and ByteCount are u32, so most of the diff is versioning-related housekeeping.

@jmcarp jmcarp force-pushed the jmcarp/block-size-docs branch 4 times, most recently from 09a9afc to 8ca839a Compare May 22, 2026 15:36
@jmcarp jmcarp force-pushed the jmcarp/block-size-docs branch from 8ca839a to 0672d1d Compare June 3, 2026 17:41
@david-crespo
Copy link
Copy Markdown
Contributor

-32k means the generation went wrong. it should be treated as a rename

@jmcarp jmcarp force-pushed the jmcarp/block-size-docs branch from 0672d1d to c5d0ad9 Compare June 3, 2026 18:03
@jmcarp jmcarp marked this pull request as ready for review June 3, 2026 18:52
},
"BlockSize": {
"title": "Disk block size in bytes",
"description": "Size of blocks for a disk. Valid values are: 512, 2048, or 4096.",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't need to effectively repeat the title in the description. I think it would be ok if it was just "description": "Valid values are: 512, 2048, or 4096.".

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ack, done.

Copy link
Copy Markdown
Contributor

@david-crespo david-crespo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. The versioning boilerplate is unfortunate but it's not complex and it seems unavoidable.

@jmcarp jmcarp force-pushed the jmcarp/block-size-docs branch from c5d0ad9 to 15bef26 Compare June 3, 2026 20:23
@jmcarp jmcarp enabled auto-merge (squash) June 3, 2026 20:25
Represent Disk::block_size as a BlockSize rather than a ByteCount, so that the
generated spec and docs are correct. This is technically a breaking change,
even though both BlockSize and ByteCount are u32, so most of the diff is
versioning-related housekeeping.
@jmcarp jmcarp force-pushed the jmcarp/block-size-docs branch from 15bef26 to dbf8d34 Compare June 4, 2026 02:13
@jmcarp jmcarp merged commit d6fba55 into main Jun 4, 2026
18 checks passed
@jmcarp jmcarp deleted the jmcarp/block-size-docs branch June 4, 2026 03:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants