docs: format the deprecation section in DOM cheatsheet #846
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
timdeschryver
approved these changes
May 24, 2021
Co-authored-by: Tim Deschryver <28659384+timdeschryver@users.noreply.github.com>
Member
|
@huyenltnguyen Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Async section on the DOM cheatsheet page has a small formatting issue which causes the
findByandfindAllByqueries to be listed as deprecated APIs. (I got a mini heart attack there to be honest)This PR formats that line a bit, so that it is part of the
waitForElementparagraph. Here is the result: