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

Fix: use standard ASPNET Core namespace for extensions #6

Merged
merged 4 commits into from
Apr 10, 2024

Conversation

seangwright
Copy link
Member

@seangwright seangwright commented Mar 25, 2024

Motivation

All DI related extension methods (extensions on IServiceCollection) should be in the same namespace - Microsoft.Extensions.DependencyInjection. This makes it easier for developers to find these extensions when they are configuring dependencies.

This PR updates the extensions in this library to follow that convention.

Checklist

  • Code follows coding conventions held in this repo
  • Automated tests have been added
  • Tests are passing
  • Docs have been updated (if applicable)
  • Temporary settings (e.g. variables used during development and testing) have been reverted to defaults

How to test

n/a

@seangwright
Copy link
Member Author

This PR requires #5 to be merged first, because the repository contains an extra .sln file which breaks the CI build.

@bkapustik
Copy link
Collaborator

This PR requires #5 to be merged first, because the repository contains an extra .sln file which breaks the CI build.

This created unused using in Dancing goat Program.cs. I have pushed a fix. Otherwise this is fine with me.

@seangwright seangwright merged commit e60e1be into main Apr 10, 2024
1 check passed
@seangwright seangwright deleted the fix/aspnet-core-conventions branch April 17, 2024 18:55
@@ -44,10 +44,10 @@ stages:
variables:
- group: Code Sign KV Auth

- name: Configuration
value: Release
- name: ProjectFolder
Copy link
Contributor

Choose a reason for hiding this comment

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

This change in indentation has broke the azure pipeline.

Copy link
Member Author

Choose a reason for hiding this comment

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

This is fixed in #5

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.

3 participants