Skip to content

Conversation

@LekoArts
Copy link
Contributor

@LekoArts LekoArts commented Apr 10, 2025

Description

With Typedoc's blockTags option you can define tags (like @important) that Typedoc should not complain about since you want to use them. I've added them in the beginning because at that time I wanted to use it for our callouts. Since then I switched over to using our markdown syntax (> [!IMPORTANT]) so it's time to remove them. And also remove their use from the source.

I've also removed the memberof because it won't do anything.

Checklist

  • pnpm test runs as expected.
  • pnpm build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

@vercel
Copy link

vercel bot commented Apr 10, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
clerk-js-sandbox ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 10, 2025 9:31am

@changeset-bot
Copy link

changeset-bot bot commented Apr 10, 2025

🦋 Changeset detected

Latest commit: b466259

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 19 packages
Name Type
@clerk/clerk-js Patch
@clerk/elements Patch
@clerk/backend Patch
@clerk/nextjs Patch
@clerk/shared Patch
@clerk/chrome-extension Patch
@clerk/clerk-expo Patch
@clerk/agent-toolkit Patch
@clerk/astro Patch
@clerk/express Patch
@clerk/fastify Patch
@clerk/nuxt Patch
@clerk/react-router Patch
@clerk/remix Patch
@clerk/tanstack-react-start Patch
@clerk/testing Patch
@clerk/expo-passkeys Patch
@clerk/clerk-react Patch
@clerk/vue Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR


To improve the in-editor experience when using Clerk's SDKs, we do our best to add [JSDoc comments](https://jsdoc.app/about-getting-started.html) to our package's public exports. The JSDoc comments should not attempt to duplicate any existing type information, but should provide meaningful additional context or references. If you are adding a new export, make sure it has a JSDoc comment. If you are updating an existing export, make sure any existing comments are updated appropriately.

There are some styleguide decisions you should follow when authoring JSDoc comments:
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This list is non-exhaustive, I'm sure I'll add more over time. But that's a good start

@LekoArts LekoArts marked this pull request as ready for review April 10, 2025 07:58
@LekoArts LekoArts merged commit 70c9db9 into main Apr 10, 2025
30 checks passed
@LekoArts LekoArts deleted the lekoarts/eco-572-remove-unusedoutdated-blocktags branch April 10, 2025 11:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants