Skip to content

Add cmdlet for Resolving Hyak and AutoRest errors #3984

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 10 commits into from
May 19, 2017

Conversation

markcowl
Copy link
Member

@markcowl markcowl commented May 17, 2017

Description


This checklist is used to make sure that common guidelines for a pull request are followed. You can find a more complete discussion of PowerShell cmdlet best practices here.

General Guidelines

  • Title of the pull request is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.
  • The pull request does not introduce breaking changes (unless a major version change occurs in the assembly and module).

Testing Guidelines

  • Pull request includes test coverage for the included changes.
  • PowerShell scripts used in tests should do any necessary setup as part of the test or suite setup, and should not use hard-coded values for locations or existing resources.

Cmdlet Signature Guidelines

  • New cmdlets that make changes or have side effects should implement ShouldProcess and have SupportShouldProcess=true specified in the cmdlet attribute. You can find more information on ShouldProcess here.
  • Cmdlet specifies OutputType attribute if any output is produced - if the cmdlet produces no output, it should implement a PassThru parameter.

Cmdlet Parameter Guidelines

  • Parameter types should not expose types from the management library - complex parameter types should be defined in the module.
  • Complex parameter types are discouraged - a parameter type should be simple types as often as possible. If complex types are used, they should be shallow and easily creatable from a constructor or another cmdlet.
  • Cmdlet parameter sets should be mutually exclusive - each parameter set must have at least one mandatory parameter not in other parameter sets.

Copy link
Member

@cormacpayne cormacpayne left a comment

Choose a reason for hiding this comment

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

@markcowl a few minor comments

Also, there should be an update to the change log


namespace Microsoft.Azure.Commands.Profile.Errors
{
[Cmdlet(VerbsDiagnostic.Resolve, "AzureRmError", DefaultParameterSetName = ResolveError.AnyErrorParameterSet)]
Copy link
Member

Choose a reason for hiding this comment

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

@markcowl does it make sense to have an alias to Resolve-Error?

{
public const string AnyErrorParameterSet = "AnyErrorParameterSet";
public const string LastErrorParameterSet = "LastErrorParameterSet";
[Parameter(Mandatory =false, Position =0, HelpMessage ="The error records to resolve", ValueFromPipeline =true, ParameterSetName = AnyErrorParameterSet)]
Copy link
Member

Choose a reason for hiding this comment

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

@markcowl nit: can we put an empty line between the last parameter set and the start of this parameter?


[Parameter(Mandatory = true, HelpMessage = "The last error", ParameterSetName = LastErrorParameterSet)]
public SwitchParameter Last { get; set; }
protected override IAzureContext DefaultContext
Copy link
Member

Choose a reason for hiding this comment

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

@markcowl nit: can we put an empty line between the last parameter and this property?

}
}

IEnumerable<ErrorRecord> GetErrorVariable()
Copy link
Member

Choose a reason for hiding this comment

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

@markcowl nit: should the below methods be private if they're only being used for this cmdlet?

Copy link
Member Author

Choose a reason for hiding this comment

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

methods with no visibility specified are automatically private


## SYNOPSIS

Display detailed information about Azure PowerShell errors.
Copy link
Member

Choose a reason for hiding this comment

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

@markcowl are the errors specific to Azure PowerShell?

Copy link
Member Author

Choose a reason for hiding this comment

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

No, we do special processing for azure powershell errors, but it is explained in the description that it applies to all errors as well


public ErrorDetails ErrorDetails { get; set; }

public ErrorCategoryInfo ErrorCategory { get; set; }
Copy link
Member

Choose a reason for hiding this comment

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

@markcowl nit: can we put an empty line between ErrorCategory and InvocationInfo?

Exception = exception;
}

public bool InnerException { get; set; }
Copy link
Member

Choose a reason for hiding this comment

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

@markcowl nit: can we put an empty line between InnerException and Exception?

}

public Uri Uri { get; set; }
public string Verb { get; set; }
Copy link
Member

Choose a reason for hiding this comment

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

@markcowl nit: can we put an empty line between Uri and Verb?

@cormacpayne
Copy link
Member

@azuresdkci test this please

cormacpayne
cormacpayne previously approved these changes May 17, 2017
@cormacpayne
Copy link
Member

cormacpayne commented May 17, 2017

On-demand: http://azuresdkci.cloudapp.net/view/1-AzurePowerShell/job/powershell-demand/1596/

Want to make sure there are no problems when generating help. LGTM once this succeeds.

@markcowl
Copy link
Member Author

@cormacpayne Is this the whitespace issue again?

@markcowl
Copy link
Member Author

@markcowl markcowl merged commit 231a559 into Azure:preview May 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants