Skip to content

Blazor: Reorganize files and prepend NationalInstruments namespace#2892

Draft
m-akinc wants to merge 8 commits intomainfrom
users/makinc/namespace-blazor
Draft

Blazor: Reorganize files and prepend NationalInstruments namespace#2892
m-akinc wants to merge 8 commits intomainfrom
users/makinc/namespace-blazor

Conversation

@m-akinc
Copy link
Contributor

@m-akinc m-akinc commented Mar 9, 2026

Pull Request

🤨 Rationale

For consistency with other NI-authored binaries, we want the Blazor assemblies from this repo to be namespaced under NationalInstruments.

Also, we want to reorganize the Blazor projects to better match the structure of the "components" packages.

👩‍💻 Implementation

  • changed namespaces and assembly names from FooBlazor to NationalInstruments.FooBlazor
  • moved components .razor and .razor.cs files into component-specific subdirectories
  • moved component-specific type files into said directories
  • moved shared files from the root into a Components/Patterns directory

🧪 Testing

Build/tests pass

@m-akinc m-akinc changed the title Prepend NationalInstruments to Blazor namespaces Blazor: Reorganize files and prepend NationalInstruments to Blazor namespaces Mar 9, 2026
@m-akinc m-akinc changed the title Blazor: Reorganize files and prepend NationalInstruments to Blazor namespaces Blazor: Reorganize files and prepend NationalInstruments namespace Mar 9, 2026
Copy link
Member

@rajsite rajsite Mar 12, 2026

Choose a reason for hiding this comment

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

Like the approach and that all the .cs source is in a subfolder since there is a decent amount of other config stuff. Only thought would be renaming the Components root folder to Source since it's not just components but also enums and various utilities. Thoughts or concerns @msmithNI @jattasNI ?

Copy link
Member

@rajsite rajsite Mar 12, 2026

Choose a reason for hiding this comment

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

For folders that are nested let's align on the naming conventions in other libraries by not repeating the full parent folder in the name, i.e TableColumn\TableColumnAnchor\ -> TableColumn\Anchor\

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet