Skip to content

docs(cdk/testing): fix broken harness predicate links #19366

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

Closed
wants to merge 1 commit into from

Conversation

howardjing
Copy link
Contributor

The links to the Filtering harness instances with HarnessPredicate
section are currently broken.

The links to the Filtering harness instances with `HarnessPredicate`
section are currently broken.
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label May 14, 2020
devversion added a commit to devversion/material2 that referenced this pull request May 15, 2020
Currently we compute the anchor ids for headings in guides and
overviews manually. Our logic here does not match with the ids generated
by Github, so one needs to either fix up all references to the anchor
for the docs, but that will break the links in most markdown editors.

We fix this by using the integrated `slugify` method provided by the
`marked` package. This one seems to match the usual id generation in
markdown files (as in Github and most markdown editors).

This fixes links in the cdk-testing harness overview as observed
originally in angular#19366.
devversion added a commit to devversion/material2 that referenced this pull request May 15, 2020
Currently we compute the anchor ids for headings in guides and
overviews manually. Our logic here does not match with the ids generated
by Github, so one needs to either fix up all references to the anchor
for the docs, but that will break the links in most markdown editors.

We fix this by using the integrated `slugify` method provided by the
`marked` package. This one seems to match the usual id generation in
markdown files (as in Github and most markdown editors).

This fixes links in the cdk-testing harness overview as observed
originally in angular#19366.
devversion added a commit to devversion/material2 that referenced this pull request May 15, 2020
Currently we compute the anchor ids for headings in guides and
overviews manually. Our logic here does not match with the ids generated
by Github, so one needs to either fix up all references to the anchor
for the docs, but that will break the links in most markdown editors.

We fix this by using the integrated `slugify` method provided by the
`marked` package. This one seems to match the usual id generation in
markdown files (as in Github and most markdown editors).

This fixes links in the cdk-testing harness overview as observed
originally in angular#19366.
@devversion
Copy link
Member

devversion commented May 15, 2020

@howardjing Thanks for this PR. I think the actual root cause for these broken links is that we have custom logic for generating anchor ids in markdown files. I sent a PR that fixes this logic, so that it aligns with the one from Github. See: #19371.

I think we can close this PR. Your contribution on this is very much appreciated!

@devversion devversion closed this May 15, 2020
devversion added a commit to devversion/material2 that referenced this pull request May 15, 2020
Currently we compute the anchor ids for headings in guides and
overviews manually. Our logic here does not match with the ids generated
by Github, so one needs to either fix up all references to the anchor
for the docs, but that will break the links in most markdown editors.

We fix this by using the integrated `slugify` method provided by the
`marked` package. This one seems to match the usual id generation in
markdown files (as in Github and most markdown editors).

This fixes links in the cdk-testing harness overview as observed
originally in angular#19366.
@howardjing
Copy link
Contributor Author

Awesome, thanks for the prompt response!

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jun 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cla: yes PR author has agreed to Google's Contributor License Agreement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants