Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

592: checking for correct assembly metadata - WIP #662

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

rohennes
Copy link
Collaborator

@rohennes rohennes commented Oct 6, 2023

Fixes #592
WIP - do not merge

@github-actions
Copy link

github-actions bot commented Oct 6, 2023

🎊 Navigate the preview: https://redhat-documentation-vale-at-red-hat-662.surge.sh 🎊

@github-actions
Copy link

github-actions bot commented Oct 6, 2023

Click here to review and test in web IDE: Contribute

@rohennes rohennes force-pushed the 592-assembly-metadata branch 2 times, most recently from 0967d95 to 289ae46 Compare October 16, 2023 14:15
@rohennes rohennes force-pushed the 592-assembly-metadata branch from 289ae46 to d14aa36 Compare October 16, 2023 14:27
@rohennes rohennes requested a review from aireilly October 16, 2023 15:24
@@ -0,0 +1,37 @@
---
extends: script
message: "Assembly is missing required metadata. Ensure you include metadata for attributes, TOC and context."
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
message: "Assembly is missing required metadata. Ensure you include metadata for attributes, TOC and context."
message: "Assembly is missing required metadata and AsciiDoc toc elements. Ensure that you include common-attributes.adoc, toc::[], and :context: attributes."

Copy link
Member

@aireilly aireilly left a comment

Choose a reason for hiding this comment

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

General comment. The rule as is implemented here catches the various errors but does not tell you which element is missing. This might be confusing for inexperienced users.

What about a series of rules, one for each element we want to police?

then we could do something like this (for example):

extends: occurrence
message: 'Assembly should have a single "toc::[]" directive'
level: error
scope: raw
min: 1
max: 1
token: toc::\[\]

image

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.

Create Vale rules for all required OCP assembly metadata
2 participants