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

made CircularDependencyExcpetion class public #5988

Merged
merged 3 commits into from
Dec 23, 2020

Conversation

tflynt91
Copy link
Contributor

@tflynt91 tflynt91 commented Dec 22, 2020

Closes #5811

@benvillalobos
Copy link
Member

@tflynt91 could you provide context for this change in the description?

@benvillalobos
Copy link
Member

##[error] After building, there are changed files. Please build locally and include these changes in your pull request. Can you run build.cmd and push up any changes?

@tflynt91
Copy link
Contributor Author

Will do!

@dnfadmin
Copy link

dnfadmin commented Dec 22, 2020

CLA assistant check
All CLA requirements met.

@dnfadmin
Copy link

CLA assistant check
Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

❌ tflynt91 sign now
You have signed the CLA already but the status is still pending? Let us recheck it.

Copy link
Member

@benvillalobos benvillalobos left a comment

Choose a reason for hiding this comment

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

The last blocker is to sign the CLA. Otherwise, LGTM!

@tflynt91
Copy link
Contributor Author

great thanks! I believe I signed it but maybe the status is still pending

Copy link
Member

@rainersigwald rainersigwald left a comment

Choose a reason for hiding this comment

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

Thanks! Just a couple of nitpicks to address.

I don't know why there are two comments about the CLA but one of them and the check are happy so I believe you signed it :)

@@ -31,7 +31,7 @@ internal CircularDependencyException(string message)
/// <summary>
/// Constructor for deserialization.
/// </summary>
protected CircularDependencyException(SerializationInfo info, StreamingContext context)
public CircularDependencyException(SerializationInfo info, StreamingContext context)
Copy link
Member

Choose a reason for hiding this comment

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

Is this change necessary? I think it's ok for this ideally-unused constructor to continue to be protected.

@@ -1,5 +1,12 @@
// Copyright (c) Microsoft. All rights reserved.
// Licensed under the MIT license. See LICENSE file in the project root for full license information.
namespace Microsoft.Build.BackEnd
Copy link
Member

Choose a reason for hiding this comment

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

We haven't exposed this namespace before, so I think we should move the exception into the Microsoft.Build.Exceptions namespace where the others are:

namespace Microsoft.Build.Exceptions
{
public partial class BuildAbortedException : System.Exception
{

Can you change the namespace in CircularDependencyException.cs?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

sounds good! I think keeping it protected was causing some error preventing it from building. The build worked on my end, I think the namespace change might resolve that, so I changed it back to protected.

Copy link
Member

@rainersigwald rainersigwald left a comment

Choose a reason for hiding this comment

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

Looks great. Thank you!

@rainersigwald rainersigwald merged commit a2c42ce into dotnet:master Dec 23, 2020
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.

Make Microsoft.Build.BackEnd.CircularDependencyException public
4 participants