-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for arrow => functions #34
Comments
Hm... Is the If you're able to do it in a reliable way with RegExp I would gladly accept it though. I'm just not very confident about that solution. |
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 |
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: