Skip to content

feat: refactor packages to use 'Framework' naming#7

Merged
thatplatypus merged 1 commit intomainfrom
feat/refactor-packges-to-framework
Dec 28, 2025
Merged

feat: refactor packages to use 'Framework' naming#7
thatplatypus merged 1 commit intomainfrom
feat/refactor-packges-to-framework

Conversation

@thatplatypus
Copy link
Contributor

The packages started out with the intent to focus on components only, but has expanded over time to include a lot of ancillary infrastructure needed to help support blazor applications. To better reflect this scope, the packages are being renamed from 'Components' to 'Framework'.

While this is a breaking change, the namespacing benefits alone should improve things long term. Mythetech.Components.Components -> Mythetech.Framework.Components reads much better for consumers using the components when importing namespaces.

The packages started out with the intent to focus on components only, but has expanded over time to include a lot of ancillary infrastructure
needed to help support blazor applications. To better reflect this scope, the packages are being renamed from 'Components' to 'Framework'.

While this is a breaking change, the namespacing benefits alone should improve things long term.
`Mythetech.Components.Components` -> `Mythetech.Framework.Components` reads much better for consumers using the components when importing namespaces.
@thatplatypus thatplatypus force-pushed the feat/refactor-packges-to-framework branch from 3afd701 to 9d89e3c Compare December 28, 2025 16:39
@thatplatypus thatplatypus merged commit b446cb1 into main Dec 28, 2025
2 checks passed
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.

1 participant