-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Add JSDoc to typings for better DX in IDEs #123
Labels
help wanted
Extra attention is needed
Comments
Sounds good to me! Though you should know that we no longer export |
Oops, I confused myself reading the docs and watching your course on FEM in parallel 😅 |
My bad 😅 |
If anyone with more experience in this wants to contribute, feel free to comment here. Else I'm going to take a stab at it on the weekend. |
4 tasks
julienw
pushed a commit
to julienw/react-testing-library
that referenced
this issue
Dec 20, 2018
Closes testing-library#122 **What**: `getByText` section in the readme. **Why**: The current example is not accurate. **How**: Since the `exact` option is true by default, I use a regular exception with ignore case to find the desired element by text. **Checklist**: - [X] Documentation - [ ] Tests N/A - [X] Ready to be merged - [X] Added myself to contributors table
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the feature you'd like:
If I start typing library functions in VS Code all I see in the IntelliSense tooltip is the import statement:
As far as I know this could be easily fixed by adding JSDoc in the
typings/index.d.ts
file so the developer quickly sees a short overview of what this function does and which parameters are expected.Suggested implementation:
I can start annotating the exported functions 🙂
Describe alternatives you've considered:
Teachability, Documentation, Adoption, Migration Strategy:
The text was updated successfully, but these errors were encountered: