docs(datatype): allow markdown in @see links

[matthewmayer]

The backtick in the @see causes the link to get broken and the second see also not to appear:

On https://next.fakerjs.dev/api/datatype.html#number

after fix:

[codecov]

Codecov Report

Merging #1667 (d969a88) into next (ec53c45) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##             next    #1667   +/-   ##
=======================================
  Coverage   99.64%   99.64%           
=======================================
  Files        2240     2240           
  Lines      240098   240098           
  Branches     1068     1068           
=======================================
  Hits       239239   239239           
  Misses        838      838           
  Partials       21       21           

[Shinigami92]

This is for rendering in VSCode tooltips

Therefore I assume instead of changing the source text, we need to somehow fix the docs automatisation text extractor

[matthewmayer]

i guess its this method? https://github.com/faker-js/faker/blob/next/scripts/apidoc/utils.ts#L114 but dont really understand what its doing or why there are two cases for a length of 1 or 3?

[matthewmayer]

previous PR where this was implemented: https://github.com/faker-js/faker/pull/1270/files

[matthewmayer]

I tried fixing the @see extraction, which works OK, although it renders like this in the docs, maybe would be better if the `` rendered as <code></code>

[ST-DDT]

You probably have to call mdToHtml somewhere.

[ST-DDT]

Thanks for fixing this.
I only have some minor nitpicking, but other than that this is ready to be merged.

[ST-DDT]

The snapshots need updating after the last typedoc/vitepress update

[ST-DDT]

The PR is still failing.