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 missing parens in requireAuth() #1713

Merged
merged 1 commit into from
Nov 15, 2024
Merged

Conversation

SuperSection
Copy link
Contributor

Correction in the naming of requireAuth() which was written as requireAuth) under the section of "requireAuth usage changes" in .

🔎 Previews:
The Page where I noticed the typo: Upgrade from Clerk's Node SDK to the Express SDK
I have attached image of the section where I made changes.
image

Explanation:

  • It's Just a typo error correction, from requireAuth) requireAuth().
  • It maintains fluency while reading the docs. Not solving much problem but rather any user reading that portion will not stumble across that noticeable error in parentheses.

This PR:

  • Corrects the format of the name requireAuth) to requireAuth()

Checklist

  • [ ✅] I have clicked on "Files changed" and performed a thorough self-review
  • [✅ ] I have added the "deploy-preview" label and added the preview link(s) to this PR description
  • [ ✅] All existing checks pass

Correction in the naming of `requireAuth()` which was written as `requireAuth)` under the section of "requireAuth usage changes".
@SuperSection SuperSection requested a review from a team as a code owner November 15, 2024 11:34
@victoriaxyz
Copy link
Contributor

Thank you for your contribution to Clerk Docs! :)

@victoriaxyz victoriaxyz changed the title Refactor requireAuth() middleware naming in node-to-express.mdx Fix missing parens in requireAuth() Nov 15, 2024
@alexisintech alexisintech merged commit 7804c0e into clerk:main Nov 15, 2024
1 check passed
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