doc: remove "considered" in errors.md#34152
Merged
Uh oh!
There was an error while loading. Please reload this page.
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
nodejs-github-bot added doc 
MemberAuthor
Trott commented Jul 2, 2020
@nodejs/documentation |
MemberAuthor
Trott commented Jul 3, 2020
@nodejs/collaborators Same. Could use some reviews. Sorry to ping widely but we don't have an errors group to ping. |
lpinca approved these changes Jul 3, 2020
cclauss approved these changes Jul 3, 2020
Flarna approved these changes Jul 3, 2020
puzpuzpuz approved these changes Jul 3, 2020
vdeturckheim approved these changes Jul 3, 2020
benjamingr approved these changes Jul 3, 2020
MrHeer approved these changes Jul 3, 2020
MemberAuthor
Trott commented Jul 3, 2020
Landed in 829f521 |
MylesBorins pushed a commit that referenced this pull request Jul 14, 2020
"would be considered a `TypeError`" -> "would be a `TypeError`". Using "considered" introduces unnecessary ambiguity. Is is not actually a TypeError but merely "considered" one? Why is that? We don't say. Simplify to "is a TypeError". PR-URL: #34152 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Christian Clauss <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Gerhard Stöbich <[email protected]> Reviewed-By: Andrey Pechkurov <[email protected]> Reviewed-By: Vladimir de Turckheim <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]>
Merged
MylesBorins pushed a commit that referenced this pull request Jul 16, 2020
"would be considered a `TypeError`" -> "would be a `TypeError`". Using "considered" introduces unnecessary ambiguity. Is is not actually a TypeError but merely "considered" one? Why is that? We don't say. Simplify to "is a TypeError". PR-URL: #34152 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Christian Clauss <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Gerhard Stöbich <[email protected]> Reviewed-By: Andrey Pechkurov <[email protected]> Reviewed-By: Vladimir de Turckheim <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]>
addaleax pushed a commit that referenced this pull request Sep 22, 2020
"would be considered a `TypeError`" -> "would be a `TypeError`". Using "considered" introduces unnecessary ambiguity. Is is not actually a TypeError but merely "considered" one? Why is that? We don't say. Simplify to "is a TypeError". PR-URL: #34152 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Christian Clauss <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Gerhard Stöbich <[email protected]> Reviewed-By: Andrey Pechkurov <[email protected]> Reviewed-By: Vladimir de Turckheim <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]>
Merged
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment
10 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.
"would be considered a
TypeError" -> "would be aTypeError".Using "considered" introduces unnecessary ambiguity. Is is not actually
a TypeError but merely "considered" one? Why is that? We don't say.
Simplify to "is a TypeError".
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes