This PR includes several improvements and refactorings to enhance readability, maintainability, and adherence to best practices within the AasxServerBlazor project. Changes include updating dependencies, renaming and restructuring files, and improving the overall codebase structure.
Motivation and Context
These changes are necessary to address a package vulnerability, improve code readability, and follow best practices. The refactoring efforts aim to make the project easier to understand and modify in the future.
Fixes # (issue)
Type of change
Please delete options that are not relevant.
[x] Bug fix (non-breaking change which fixes an issue)
How Has This Been Tested?
These changes have been tested locally by running the application and ensuring that all functionalities work as expected. Additionally, existing unit tests have been run to ensure no regressions are introduced. Manual testing was performed to verify that the refactored components behave correctly.
Screenshots (if appropriate):
Checklist:
[x] My code follows the style guidelines of this project
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works
Description
This PR includes several improvements and refactorings to enhance readability, maintainability, and adherence to best practices within the AasxServerBlazor project. Changes include updating dependencies, renaming and restructuring files, and improving the overall codebase structure.
Motivation and Context
These changes are necessary to address a package vulnerability, improve code readability, and follow best practices. The refactoring efforts aim to make the project easier to understand and modify in the future.
Fixes # (issue)
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
These changes have been tested locally by running the application and ensuring that all functionalities work as expected. Additionally, existing unit tests have been run to ensure no regressions are introduced. Manual testing was performed to verify that the refactored components behave correctly.
Screenshots (if appropriate):
Checklist: