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

fix the toc for securing webhooks #2759

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

Conversation

lyleschemmerling
Copy link
Collaborator

So in order to get that toc to populate needed to add the nested headings frontmatter param and export the headings from the sub component. Our implementation of the TOC expected some h2s and not only h3s so I changed those to make them populate and think that it looks okay, but am interested in what you think.

Related:

Copy link
Contributor

Choose a reason for hiding this comment

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

Would be awesome to correct this name to _securing-http-requests.mdx to conform to our standards.

@@ -1,11 +1,11 @@
---
---
### TLS v1.2
## TLS v1.2
Copy link
Contributor

Choose a reason for hiding this comment

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

This breaks the outline of the two other places this is used

grep -Rl _securing_http_requests
./extend/events-and-webhooks/securing.mdx
./lifecycle/migrate-users/connectors/generic-connector.mdx
./customize/email-and-messages/generic-messenger.mdx

Suggest we keep it at an h3 and add another header in there. I can take a swing at this if you'd like. (We need to add in the webhook signing section anyway.)


## Securing Webhooks
export const headings = securing.getHeadings();
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we need to do this for the other two places we include this file?

@mooreds
Copy link
Contributor

mooreds commented Jan 4, 2024

@lyleschemmerling any plans to make changes?

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.

None yet

2 participants