Skip to content
This repository was archived by the owner on Nov 6, 2018. It is now read-only.

expose NoopChangeToken, NotFoundDirectoryContents, NotFoundFileInfo as public #195

Merged
merged 1 commit into from
May 26, 2016

Conversation

Driedas
Copy link
Contributor

@Driedas Driedas commented May 25, 2016

changes as per the discussion on issue #145

unit tests passing (executed via dotnet test)

@dnfclas
Copy link

dnfclas commented May 25, 2016

Hi @Driedas, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla2.dotnetfoundation.org.

TTYL, DNFBOT;

@dnfclas
Copy link

dnfclas commented May 25, 2016

@Driedas, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.

Thanks, DNFBOT;

@@ -6,7 +6,7 @@

namespace Microsoft.Extensions.FileProviders
{
internal class NoopChangeToken : IChangeToken
public class NoopChangeToken : IChangeToken
Copy link
Contributor

Choose a reason for hiding this comment

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

Naming concern since we're making this type public - should this be called NullChangeToken? We name other things similarly e.g. NullLogger for things that don't do much. Thoughts @Eilon ?

Copy link
Member

Choose a reason for hiding this comment

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

Yeah I suppose this is basically the Null Pattern.

@Eilon
Copy link
Member

Eilon commented May 26, 2016

@pranavkm do we need a bunch of reaction PRs in other repos for this? I suspect this might be a slightly destabilizing change due to other repos needing to react to this.

@Eilon
Copy link
Member

Eilon commented May 26, 2016

Oh actually I wonder if perhaps this is totally safe because the type is moving from being internal in .Sources to being public in the main package. So presumably it's just a switcheroo and perhaps safe...

@pranavkm
Copy link
Contributor

Yeah, the move should be fine and the rename too since it doesn't look like it's used outside of this repo.

@Driedas
Copy link
Contributor Author

Driedas commented May 26, 2016

@pranavkm renamed the NoopChangeToken to NullChangeToken and added the comment for NotFoundDirectoryContents, as per your comments
Have tried to come up with a reasonable comment for the NullChangeToken as well, that didn't involve the word "fake" or "stub", as these are mostly associated with *testing, but I have nothing better than "An empty change token that doesn't raise any change callbacks"

@pranavkm
Copy link
Contributor

@Driedas that sounds good.

@pranavkm
Copy link
Contributor

Let me know when you've have added the resx string and I'll merge this in.

@Driedas
Copy link
Contributor Author

Driedas commented May 26, 2016

@pranavkm comment added
Do you want me to squash the commits into a single one or is it ok like this?

@pranavkm
Copy link
Contributor

Squashing it would be great.

@Driedas
Copy link
Contributor Author

Driedas commented May 26, 2016

done...

@pranavkm pranavkm merged commit f282bce into aspnet:dev May 26, 2016
@pranavkm
Copy link
Contributor

Thanks!

@Eilon
Copy link
Member

Eilon commented May 26, 2016

@Driedas thanks for the PR!

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

Successfully merging this pull request may close these issues.

4 participants