Skip to content

Align coding style #32

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

Merged
merged 1 commit into from
Jun 9, 2017
Merged

Align coding style #32

merged 1 commit into from
Jun 9, 2017

Conversation

CVipulS
Copy link

@CVipulS CVipulS commented May 16, 2017

The last instantiation of call line #42 had mismatched showing filter's return value with the two previous instantiations lines #19, #30 from the same code block.

The last instantiation of call had mismatched showing filter's return value with the two previous instantiations from the same code block.
@msftclas
Copy link

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

Copy link
Contributor

@mikeblome mikeblome left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, yes it's better that all lambdas have same conventions even though the explicit return value is not necessary on any of them.

@mikeblome mikeblome merged commit 9726e70 into MicrosoftDocs:master Jun 9, 2017
@CVipulS
Copy link
Author

CVipulS commented Jun 11, 2017

Agreed. I must mention, the reasoning to elect lookup ease from retaining the explicit return value was this being canonical documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants