Skip to content
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

Treat arrow functions in the same way as explicit functions #39

Open
antoinetissier opened this issue Mar 1, 2022 · 0 comments
Open
Labels
enhancement New feature or request ⚡ good first issue Good for newcomers 🐎 priority

Comments

@antoinetissier
Copy link
Collaborator

antoinetissier commented Mar 1, 2022

Whether I implement my function as const myFunction = () => {} or function myFunction(){}, I expect it to be documented in the same way.
For example, getParentPaths should end up in the "Functions" page instead of the "Variables" page, and its signature should be properly documented.

Could be fixed at the source by microsoft/rushstack#1629

@Nouzbe Nouzbe added the enhancement New feature or request label Feb 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request ⚡ good first issue Good for newcomers 🐎 priority
Projects
None yet
Development

No branches or pull requests

3 participants