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
This could be fixed easy by supplying a regular expression for ES6 arrow functions which would then change the context to function.
Right in the same way (with some regular expressions ) support for async/await can be added. As discussed here: #31.
Yeah you're probably right that all those RegExpes do not belong here. I am just not confident that a pull request would be accepted in tj/dox because the activity there is low.
However I am half-way through in upgrading my fork of dox with async and arrow functions. It is not that difficult with the work @cjy37 has done but writing the missing tests takes time...
On the topic of async functions I'd really like to see the promise syntax ~>~!>@jmatsushita has implemented in his fork of jsdoctest to be supported. But I don't know if he's done more than this syntactic improvement that cannot be merged back to jsdoctest.
is not recognised by jsdoctest ("0 passing") because dox.js detects a declaration:
This could be fixed easy by supplying a regular expression for ES6 arrow functions which would then change the context to
function
.Right in the same way (with some regular expressions ) support for async/await can be added. As discussed here: #31.
Where should this happen? Should I prepare a pull request into dox.js or into jsdoctest by using the dox api for context matching?
I'd prefer patching
getJsdoctests()
here.The text was updated successfully, but these errors were encountered: