-
Notifications
You must be signed in to change notification settings - Fork 682
Makes VolumeNameGenerator public #6531
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
Conversation
Co-authored-by: Dan Moseley <danmose@microsoft.com>
/// <param name="builder">The resource builder.</param> | ||
/// <param name="suffix">The suffix to append to the volume name.</param> | ||
/// <returns>The volume name.</returns> | ||
/// <exception cref="ArgumentException"></exception> | ||
public static string CreateVolumeName<T>(IResourceBuilder<T> builder, string suffix) where T : IResource |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably want to think about naming here.. duplicative ? VolumeNameGenerator.Generate
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have no preference on this, simply changed the visibility. I agree though, Generate seems more consistent and it’s an opportunity to polish it a bit. I’ll update it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have updated to change the name from CreateVolumeName to Generate as suggested.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@danmoseley Are you good with the changes made?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
seems fine to me. @davidfowl what is the process around public API naming - is this OK?
cc @DamianEdwards as he wrote this code |
Co-authored-by: Damian Edwards <damian@damianedwards.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks
@los93sol if you put text like Thanks for the contribution, we'd welcome more. |
Makes VolumeNameGenerator public #6490
Microsoft Reviewers: Open in CodeFlow