Is your feature request related to a problem? Please describe
In my component's props TS interface, I can use JSDoc comments to set the description, and can even use the @default tag to describe the default value 💯
However, nothing happens when I use the @deprecated tag.

Describe the solution you'd like
Some ideas:

• It would be nice i

Hi, I've found the following cheatsheet :

In the README you explain that there must be an edit button in the page and a github button to access the sheet but as you can see it doesn't appear here.

Thx ;)

🐛 Bug Report

I started to use docusaurus for an existing documentation which has apostrophes in filenames sometimes.
When I build my project, I always have the following error:

SyntaxError: docusaurus2/.docusaurus/routes.js: Unexpected token, expected ","
{
  path: '/docs/Wiki/Project's-Guide',
  component: ComponentCreator('/docs2/Wiki/Project's-Guide','efe'),
  exact: true,
}

Bug Report

Current behavior

I think there's a mismatch of environment variables being read by babel (JSX config) and Styleguidist, causing some issues deeper down.

(I've noticed this was raised before but was closed)

• build.js sets the env to be production here: https://github.com/styleguidist/react-styleguidist/blob/master/src/s

I was just contributing to the docs a few minutes ago and after running

yarn check

got this warning

"The prop value with an expression type of SequenceExpression could not be resolved. Please file issue to get this fixed immediately." .

Thought I'd let you know.

Search Terms

Category, @category, hide, internal,

Problem

I would like to have an additional option to hide certain categories.

There is an existing typedoc option --stripInternal based on the tag @internal.
But this is not very flexible and it is actually based on a TypeScript compiler option which causes declara