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

🚀 Feature

Feature request from Canny:

I think the back to top button in the v1 should be also implemented in v2. Long docs will ne

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 ;)

Feature request

An option to put the sidebar on the right instead of the left

Current behavior

When stylegudist is configured to use a font size for base and/or text to be anything other than 16px, the paragraph content generated from markdown does not use the specified font size.

Question: Is a markdown paragraph considered to be either base or text? I am assuming it should be text at the very least.

To reproduce

1. Config:

   module.
   

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

Optional type, optional parameters,

Problem

TypeScript 3.0 added support for Optional elements in tuple types, but TypeDoc didn't get support at the same time.

Checklist

• Add a new Type model for optional types
• Add a test for `type T