-
Notifications
You must be signed in to change notification settings - Fork 4.3k
Docs: mention trace viewer as debugging tool for the Mouse API class #35857
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
Conversation
Signed-off-by: Gwenn Le Bihan <[email protected]>
Co-authored-by: Max Schmitt <[email protected]> Signed-off-by: Gwenn Le Bihan <[email protected]>
Co-authored-by: Max Schmitt <[email protected]> Signed-off-by: Gwenn Le Bihan <[email protected]>
@gwennlbh, this PR is stalled as your change isn't passing our linter. It looks like your link paths aren't correct. |
ok so i figured it out -- i see two problems with the linter:
|
@microsoft-github-policy-service agree |
This comment has been minimized.
This comment has been minimized.
|
latest lint error comes from a diff in the generated .d.ts files that include docs as part of their docstring comments, this is a clean tree check that runs after lints, so the path lookup does not fail anymore |
Test results for "tests 1"1 failed 5 flaky39318 passed, 818 skipped Merge workflow run. |
Thanks! |
I had to go search this and found out about this way of seeing where the mouse is through #16546
Putting it in the docs will save people some time :)