You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should definitely do 4, and further I think we should drop the mapping concept altogether, and instead improve the search capability so it could look for metadata and not just function names so that searching for the lodash or ramda name would bring up the equivalent function.
I think instead of @lodash and @ramda it would need to be a @mapping tag and we'd configure it to take a param and additional text so that it could be written as:
* @mapping<library>[renamedName][-additionalcontext/differences/notes]// Exact copy:* @mappinglodash// Renamed/changes:* @mappingramdacond-add`defaultCase()`aslastcase// flexible to other libraries we can map to, Hack Standard Library, Python, Go, C, Java, etc...* @mappingpythonzip-returnsanarray,notaniterator
it'd be nice to have the mapping on the docs website; right now it's not mentioned
options:
index.astro
(aside: this has diverged from the repoREADME.md
; should that be changed?)mapping.md
to a file that we can indocs/src/data
, then read it formapping.astro
mapping.md
with a data file indocs/src/data
, then read it formapping.astro
@lodash
and@ramda
, then read existing jsdoc output formapping.astro
(and other options are possible too)
i personally like 4
The text was updated successfully, but these errors were encountered: