Skip to content
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

[StyleCop] Fix stylecop warnings on Bot.Builder.TestBot.WebApi #1642

Merged
merged 1 commit into from
Apr 9, 2019

Conversation

gasper-az
Copy link
Contributor

Resolve stylecop issues on Bot.Builder.TestBot.WebApi

Changes made:

  • Formatting and spacing
  • Resolve version of the dependent assembly
  • Ignore SA issue maintaining the protectedness

@gasper-az gasper-az changed the title [StyleCop] Fix stylecop warnings onBot.Builder.TestBot.WebApi [StyleCop] Fix stylecop warnings on Bot.Builder.TestBot.WebApi Apr 8, 2019
@coveralls
Copy link
Collaborator

Pull Request Test Coverage Report for Build 53587

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 76.126%

Totals Coverage Status
Change from base Build 53546: 0.0%
Covered Lines: 4362
Relevant Lines: 5730

💛 - Coveralls

@cleemullins
Copy link
Contributor

No issues found in Microsoft.Bot.Builder.dll
No issues found in Microsoft.Bot.Builder.AI.Luis.dll
No issues found in Microsoft.Bot.Builder.AI.QnA.dll
No issues found in Microsoft.Bot.Builder.ApplicationInsights.dll
No issues found in Microsoft.Bot.Builder.Azure.dll
No issues found in Microsoft.Bot.Builder.Dialogs.dll
No issues found in Microsoft.Bot.Builder.TemplateManager.dll
No issues found in Microsoft.Bot.Configuration.dll
No issues found in Microsoft.Bot.Connector.dll
No issues found in Microsoft.Bot.Schema.dll

Copy link
Contributor

@cleemullins cleemullins left a comment

Choose a reason for hiding this comment

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

LGTM. This is all great stuff.

@cleemullins cleemullins merged commit ec9bac3 into master Apr 9, 2019
@cleemullins cleemullins deleted the fix/stylecop/Builder-TestBot-WebApi branch April 9, 2019 04:24
protected readonly Dialog _dialog;
protected readonly BotState _conversationState;
protected readonly BotState _userState;
protected readonly ILogger _logger;
#pragma warning restore SA1401 // Fields should be private
Copy link
Member

Choose a reason for hiding this comment

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

This code is an exact drop of the core bot sample (in this case the webapi sample)

It would be great if we can maintain the consistency, that makes updates much easier. So can we exclude this warning outside of the code in an external rules file. That is possible with stylecop isn't it?

{
DestinationStepAsync,
OriginStepAsync,
TravelDateStepAsync,
ConfirmStepAsync,
FinalStepAsync,
}));
};
AddDialog(new WaterfallDialog(nameof(WaterfallDialog), steps));
Copy link
Member

Choose a reason for hiding this comment

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

Why?
Can we just keep this consistent with the original sample?
Specifically, sure if you want to make this change for some reason can you also make it in the sample.

{
InitialStepAsync,
FinalStepAsync,
}));
Copy link
Member

Choose a reason for hiding this comment

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

ditto


// The initial child Dialog to run.
InitialDialogId = nameof(WaterfallDialog);
}

private static Task<bool> DateTimePromptValidator(PromptValidatorContext<IList<DateTimeResolution>> promptContext, CancellationToken cancellationToken)
Copy link
Member

Choose a reason for hiding this comment

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

Why move this?
The original order was intentional. we can move it if you like but exactly why would we do that?
(and again consistency with the original sample)

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.

None yet

4 participants