[ Lifecycle ] Increase importance of logging errors #410
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
"errors, if any, MAY be logged" --> "errors, if any, SHOULD be logged" Signed-off-by: Rob Dolin <RobDolin@microsoft.com>
Contributor
|
On Thu, Apr 28, 2016 at 03:08:11PM -0700, Rob Dolin (MSFT) wrote:
I don't think this is particularly important until we get more clarity |
Member
|
LGTM |
Mashimiao
pushed a commit
to Mashimiao/specs
that referenced
this pull request
Aug 19, 2016
"errors, if any, MAY be logged" --> "errors, if any, SHOULD be logged" Signed-off-by: Rob Dolin <RobDolin@microsoft.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
"errors, if any, MAY be logged" --> "errors, if any, SHOULD be logged"
Signed-off-by: Rob Dolin RobDolin@microsoft.com