-
Notifications
You must be signed in to change notification settings - Fork 92
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
fix: Markdownlint #702
fix: Markdownlint #702
Conversation
Signed-off-by: Brendan Cronin <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but please check if the title or id is used for header generation. THX
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The build of the website fails which should be fixed before merging.
Signed-off-by: Brendan Cronin <[email protected]>
@bcronin90 the page can't be built, cause in the sidebarsDocsKits.js you reference to files/ids which are not present right now Error: Error: Invalid sidebar file at "sidebarsDocsKits.js".
These sidebar document ids do not exist:
- kits/Connector Kit/Development View/specifications
- kits/Connector Kit/Operation View/operation-view Two options, rename the ids in the related files or change the reference. I think the ID itself shouldnt be changed, cause it is used for the headline? |
The "title" field is used for the headline, which is why it caused duplication warnings in the linter. The "id" field is purely for under-the-hood stuff. While I was removing the titles, I added ids where there weren't any. Apparently that broke something somewhere. So I'll revert that. |
Signed-off-by: Brendan Cronin <[email protected]>
Signed-off-by: Brendan Cronin <[email protected]>
So about this one:
Turns out it's not a false positive, just a bit misleading. We had a wrong bracket type in there. Yay for linting. |
Okay, all Markdown errors should be from outside our scope now. |
@bcronin90 I built the page locally and i am not sure if this is related to the changes with the IDs, but the architecture page shows the headline twice ![]() Definitely, this has nothing to do with the markdown :) |
Might be something in one of the sidebars js' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR removes the title in different files. Therefore, it doesn't get displayed with an uppercase starting letter. This has nothing to do with the sidebar file.
So what's the best practice here? Cause if I add it again, I get the duplicate header warning from the markdown linter, which this was supposed to remove. I can remove the actual markdown header instead. But instead of stumbling in the dark some more, I'll just ask: What's our general approach here? |
I suggest having a look at all the other KITs. Most KITs (what I would suggest) are using
Please keep in mind to use a unique ID (not just |
Signed-off-by: Brendan Cronin <[email protected]>
Not sure, is there still something todo here? |
The current branch can't be merged because the "Verify website build" stage is still failing. |
Ah. I wasn't aware we explicitly linked each document again. I'll fix those links. |
Signed-off-by: Brendan Cronin <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the fix!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Fix markdownlint issues
Closes #692
MD053 in adoption-view.md looks like a false positive to me.