Skip to content

Conversation

@karenetheridge
Copy link
Member

No description provided.

Copy link
Member

@handrews handrews left a comment

Choose a reason for hiding this comment

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

@karenetheridge thanks again for working on the Learn site! I went through all of the non-.dot files in detail.

I started fixing broken camelCase links (not broken because of your change), but once i finished the non-.dot files and went back to check those, I realized it was a much bigger effort and perhaps a bit of search-and-replace on your end might be better than me clicking through 100 or so more GitHub suggestions. Or we can do these as a separate fix later.

I did check on the links to sections that weren't Object headings, and the few present here are indeed still present in 3.2.

@karenetheridge
Copy link
Member Author

I was actually going to suggest that we have a script (perhaps driven by a GH action) that extracts all the spec links from the learn site and adds them to a list to check that they keep existing. ;)

@karenetheridge karenetheridge marked this pull request as draft January 29, 2026 17:06
@karenetheridge
Copy link
Member Author

New commits pushed which correct the bad links.

@karenetheridge karenetheridge marked this pull request as ready for review January 30, 2026 22:35
via:

perl -p -i -e's{/oas/latest#\K([a-zA-Z]+)\b}{lc join("-", split /(?=[A-Z])/, $1)}ge' `find * -type f`
via:

perl -p -i -e's/oas-object/openapi-object/g' `find * -type f`
@lornajane
Copy link
Contributor

I can add a linkchecker if that's useful? We might even already have a ticket open and I just didn't actually do it yet ....

@karenetheridge
Copy link
Member Author

I had a linkchecker running locally that exercises all the links to check for a 404, but the problem in this case is that the anchor links were wrong, which requires having the local document in hand to check that the anchor goes to a defined location within the document.

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.

3 participants