Merge pull request #4 from PhanCongVuDuc/ducphan/Code-Clean

Feature/Code clean

Author: PhanCongVuDuc

.editorconfig

@@ -23,7 +23,7 @@ generated_code = true
 # C# files
 [*.cs]
 # New line preferences
-csharp_new_line_before_open_brace = all
+csharp_new_line_before_open_brace = accessors, anonymous_methods, anonymous_types, events, indexers, lambdas, local_functions, methods, object_collection_array_initializers, types
 csharp_new_line_before_else = true
 csharp_new_line_before_catch = true
 csharp_new_line_before_finally = true

CODE_OF_CONDUCT.md

@@ -2,7 +2,10 @@
 
 ## Our Pledge
 
-We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for
+everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity
+and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion,
+or sexual identity and orientation.
 
 We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
 
@@ -26,41 +29,62 @@ Examples of unacceptable behavior include:
 
 ## Enforcement Responsibilities
 
-Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take
+appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
 
-Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits,
+issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any
+contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
 
 ## Scope
 
-This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing
+the community in public spaces. Examples of representing our community include using an official e-mail address, posting
+via an official social media account, or acting as an appointed representative at an online or offline event.
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement by creating a [GitHub Issue](https://github.com/PhanCongVuDuc/Sonny/issues/new) with the `code-of-conduct` label. All complaints will be reviewed and investigated promptly and fairly.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible
+for enforcement by creating a [GitHub Issue](https://github.com/PhanCongVuDuc/Sonny/issues/new) with the
+`code-of-conduct` label. All complaints will be reviewed and investigated promptly and fairly.
 
 All community leaders are obligated to respect the privacy and security of the reporter of any incident.
 
 ## Enforcement Guidelines
 
-Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem
+in violation of this Code of Conduct:
 
 ### 1. Correction
-**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
 
-**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the
+community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation
+and an explanation of why the behavior was inappropriate. A public apology may be requested.
 
 ### 2. Warning
+
 **Community Impact**: A violation through a single incident or series of actions.
 
-**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including
+unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding
+interactions in community spaces as well as external channels like social media. Violating these terms may lead to a
+temporary or permanent ban.
 
 ### 3. Temporary Ban
+
 **Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
 
-**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified
+period of time. No public or private interaction with the people involved, including unsolicited interaction with those
+enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
 
 ### 4. Permanent Ban
-**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate
+behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
 
 **Consequence**: A permanent ban from any sort of public interaction within the community.
 

CONTRIBUTING.md

@@ -28,34 +28,42 @@ We love new ideas! Please create an issue with:
 
 This project follows the **Git Flow** branching model with the following branches:
 
-- **`master`**: Production-ready code. Only stable, tested releases are merged here. This branch should always be deployable.
-- **`develop`**: Integration branch for features. All feature branches merge into this branch. This is the main development branch.
+- **`master`**: Production-ready code. Only stable, tested releases are merged here. This branch should always be
+  deployable.
+- **`develop`**: Integration branch for features. All feature branches merge into this branch. This is the main
+  development branch.
 - **`feature/*`**: Feature branches for new functionality. Created from and merged back into `develop`.
-- **`release/*`**: Release branches for preparing new production releases. Created from `develop` and merged into both `master` and `develop`.
-- **`hotfix/*`**: Hotfix branches for urgent production bug fixes. Created from `master` and merged into both `master` and `develop`.
+- **`release/*`**: Release branches for preparing new production releases. Created from `develop` and merged into both
+  `master` and `develop`.
+- **`hotfix/*`**: Hotfix branches for urgent production bug fixes. Created from `master` and merged into both `master`
+  and `develop`.
 
 #### Git Flow Diagram
 
 ![Git Flow Branching Model](assets/images/gitflow.png)
 
-*Visual representation of the Git Flow branching model showing how commits flow between master, develop, feature, release, and hotfix branches.*
+*Visual representation of the Git Flow branching model showing how commits flow between master, develop, feature,
+release, and hotfix branches.*
 
 #### Branch Usage Guidelines
 
 **Feature Branches:**
+
 - Created from `develop`
 - Used for developing new features
 - Merged back into `develop` via Pull Request
 - Naming convention: `feature/feature-name` (e.g., `feature/add-new-tool`)
 
 **Release Branches:**
+
 - Created from `develop` when preparing a new release
 - Used for final bug fixes and release preparations
 - Merged into both `master` (with version tag) and `develop`
 - Naming convention: `release/version-number` (e.g., `release/v1.0.0`)
 - Only maintainers create release branches
 
 **Hotfix Branches:**
+
 - Created from `master` for urgent production fixes
 - Used for critical bug fixes that cannot wait for the next release
 - Merged into both `master` (with version tag) and `develop`
@@ -65,20 +73,23 @@ This project follows the **Git Flow** branching model with the following branche
 ### Pull Requests
 
 **Workflow Overview:**
+
 1. Fork the repository and clone it locally
 2. Create a feature branch from `develop` (see Git Flow diagram above)
 3. Make your changes and commit them
 4. Push your feature branch to your fork
 5. Create a Pull Request targeting `develop` branch
 
 **Important Guidelines:**
+
 - **Always create feature branches from `develop`**, not from `master`
 - **Pull requests must target `develop` branch** (not `master`)
 - Only maintainers merge `develop` into `master` for releases
 - Keep your feature branch up to date with `develop` before creating PR
 
 **Commit Message Format:**
 Use clear commit messages following this format:
+
 - `Add:` for new features
 - `Fix:` for bug fixes
 - `Update:` for updates to existing features
@@ -87,6 +98,7 @@ Use clear commit messages following this format:
 - `Test:` for test additions or changes
 
 **When Creating a Pull Request:**
+
 - Describe what your PR does
 - Reference any related issues (use `Closes #123` or `Fixes #123`)
 - Include screenshots if UI changes
@@ -96,12 +108,14 @@ Use clear commit messages following this format:
 ### Release & Hotfix Branches (Maintainers Only)
 
 **Release Branches:**
+
 - Created from `develop` when preparing a new release
 - Used for final bug fixes and release preparations
 - Merged into both `master` (with version tag) and `develop`
 - See Git Flow diagram above for visual workflow
 
 **Hotfix Branches:**
+
 - Created from `master` for urgent production bug fixes
 - Used for critical fixes that cannot wait for the next release
 - Merged into both `master` (with version tag) and `develop`
@@ -114,9 +128,9 @@ Use clear commit messages following this format:
 - Follow the `.editorconfig` settings
 - Use meaningful variable and method names
 - Follow C# naming conventions:
-  - PascalCase for classes, methods, properties
-  - camelCase for local variables
-  - _camelCase for private fields
+    - PascalCase for classes, methods, properties
+    - camelCase for local variables
+    - _camelCase for private fields
 - Add XML documentation comments for public APIs
 - Keep methods focused and small
 - Use `var` when type is apparent
@@ -153,10 +167,10 @@ public double FromInternalUnit(double value, ForgeTypeId displayUnit)
 ## Development Setup
 
 1. Install prerequisites:
-   - .NET Framework 4.8
-   - .NET 9 SDK
-   - Visual Studio or JetBrains Rider
-   - Revit (for testing)
+    - .NET Framework 4.8
+    - .NET 9 SDK
+    - Visual Studio or JetBrains Rider
+    - Revit (for testing)
 
 2. Clone repository with submodules:
    ```bash
@@ -182,6 +196,7 @@ public double FromInternalUnit(double value, ForgeTypeId displayUnit)
 ## Questions?
 
 If you have questions about contributing, please:
+
 - Open an issue with the `question` label
 - Check existing issues and discussions
 - Review the README.md for more information

Changelog.md

@@ -1,17 +1,20 @@
 # 1.0.0
 
 ## Features
+
 - ✨ **AutoColumnDimension** - Automatically create dimensions for columns in Revit
 - 🌐 **Multi-language Support** - Multi-language support with ResourceDictionary and WPFLocalizeExtension
 - ⚙️ **Settings Dialog** - Settings dialog for the plugin
 - 🔧 **Multi-version Support** - Support for Revit 2021 - 2026
 - 📏 **Multiple Units Support** - Support for multiple measurement units (feet, meters, inches, etc.)
 
 ## Architecture
+
 - 🏗️ **Dependency Injection** - Using Microsoft.Extensions.DependencyInjection
 - 🎨 **MVVM Pattern** - Implementing MVVM with CommunityToolkit.Mvvm
 - 🧪 **Unit Testing** - Testing framework with NUnit and NSubstitute
 
 ## Build & Development
+
 - 🛠️ **Build Automation** - Build automation with Nuke
-- 📦 **MSBuild Customization** - Custom MSBuild targets and tasks
+- 📦 **MSBuild Customization** - Custom MSBuild targets and tasks

Readme.md

@@ -15,11 +15,13 @@ Sonny is an **open source** project built with the following goals:
 - 🤝 **Community**: Together we develop, share knowledge and experiences
 - 🆓 **Free**: Create free tools for everyone to use
 
-This project focuses on developing useful tools for the Revit community, with open source code so that everyone can learn, contribute, and use freely.
+This project focuses on developing useful tools for the Revit community, with open source code so that everyone can
+learn, contribute, and use freely.
 
 ## Table of content
 
 <!-- TOC -->
+
 * [What You Can Learn](#what-you-can-learn)
 * [Videos](#videos)
 * [Prerequisites](#prerequisites)
@@ -31,6 +33,7 @@ This project focuses on developing useful tools for the Revit community, with op
 * [License](#license)
 * [Security](#security)
 * [Acknowledgments](#acknowledgments)
+
 <!-- TOC -->
 
 ## What You Can Learn
@@ -80,7 +83,8 @@ After installation, clone this repository to your local machine and navigate to
 
 ## Cloning the Repository
 
-This project uses **Git Submodule** to manage dependencies. The following libraries are included as submodules from their own repositories:
+This project uses **Git Submodule** to manage dependencies. The following libraries are included as submodules from
+their own repositories:
 
 - **Revit.Async** - Async utilities for Revit API
 - **Sonny.EasyRibbon** - Attribute-based framework for creating Revit Ribbon UI
@@ -117,25 +121,29 @@ git push origin master
 This project includes the following submodules:
 
 #### Revit.Async
+
 - **Submodule location**: `source/Revit.Async`
 - **Submodule repository**: [Revit.Async](https://github.com/PhanCongVuDuc/Revit.Async)
 - The submodule tracks a specific commit from the Revit.Async repository
 - Changes to Revit.Async should be committed in its own repository, not in Sonny
 
 #### Sonny.EasyRibbon
+
 - **Submodule location**: `source/Sonny.EasyRibbon`
 - **Submodule repository**: [Sonny.EasyRibbon](https://github.com/PhanCongVuDuc/Sonny.EasyRibbon)
 - The submodule tracks a specific commit from the Sonny.EasyRibbon repository
 - Changes to Sonny.EasyRibbon should be committed in its own repository, not in Sonny
 
 #### Sonny.RevitExtensions
+
 - **Submodule location**: `source/Sonny.RevitExtensions`
 - **Submodule repository**: [Sonny.RevitExtensions](https://github.com/PhanCongVuDuc/Sonny.RevitExtensions)
 - The submodule tracks a specific commit from the Sonny.RevitExtensions repository
 - Changes to Sonny.RevitExtensions should be committed in its own repository, not in Sonny
 
 > [!NOTE]
-> If you see empty submodule folders after cloning, you need to initialize submodules using `git submodule update --init --recursive`
+> If you see empty submodule folders after cloning, you need to initialize submodules using
+`git submodule update --init --recursive`
 
 ## Solution Structure
 
@@ -160,11 +168,14 @@ For detailed documentation, see [RevitTemplates Wiki](https://github.com/Nice3po
 
 This project uses the following libraries and tools:
 
-- **[RevitTemplates](https://github.com/Nice3point/RevitTemplates)** - Project templates and build system for Revit plugins
+- **[RevitTemplates](https://github.com/Nice3point/RevitTemplates)** - Project templates and build system for Revit
+  plugins
 - **[Revit.Async](https://github.com/PhanCongVuDuc/Revit.Async)** - Async utilities for Revit API
 - **[RevitTest](https://github.com/ricaun-io/RevitTest)** - Testing framework for Revit applications
-- **[Sonny.EasyRibbon](https://github.com/PhanCongVuDuc/Sonny.EasyRibbon)** - Attribute-based framework for creating Revit Ribbon UI
-- **[Sonny.RevitExtensions](https://github.com/PhanCongVuDuc/Sonny.RevitExtensions)** - Revit API extension methods and utilities library
+- **[Sonny.EasyRibbon](https://github.com/PhanCongVuDuc/Sonny.EasyRibbon)** - Attribute-based framework for creating
+  Revit Ribbon UI
+- **[Sonny.RevitExtensions](https://github.com/PhanCongVuDuc/Sonny.RevitExtensions)** - Revit API extension methods and
+  utilities library
 
 ## Contributing
 
@@ -183,12 +194,16 @@ This project is licensed under the MIT License - see the [LICENSE](LICENSE) file
 
 ## Security
 
-If you discover a security vulnerability, please see our [Security Policy](SECURITY.md) for information on how to report it.
+If you discover a security vulnerability, please see our [Security Policy](SECURITY.md) for information on how to report
+it.
 
 ## Acknowledgments
 
 We would like to express our gratitude to the creators of the following open-source libraries:
 
-- **[RevitTemplates](https://github.com/Nice3point/RevitTemplates)** by [Nice3point](https://github.com/Nice3point) - Project templates and build system for Revit plugins
-- **[Revit.Async](https://github.com/PhanCongVuDuc/Revit.Async)** by [KennanChan](https://github.com/KennanChan) - Async utilities for Revit API
-- **[RevitTest](https://github.com/ricaun-io/RevitTest)** by [ricaun-io](https://github.com/ricaun-io) - Testing framework for Revit applications
+- **[RevitTemplates](https://github.com/Nice3point/RevitTemplates)** by [Nice3point](https://github.com/Nice3point) -
+  Project templates and build system for Revit plugins
+- **[Revit.Async](https://github.com/PhanCongVuDuc/Revit.Async)** by [KennanChan](https://github.com/KennanChan) - Async
+  utilities for Revit API
+- **[RevitTest](https://github.com/ricaun-io/RevitTest)** by [ricaun-io](https://github.com/ricaun-io) - Testing
+  framework for Revit applications

SECURITY.md

@@ -6,9 +6,11 @@ Only the latest version receives security patches.
 
 ## Reporting a Vulnerability
 
-Please report security vulnerabilities by creating a [GitHub Issue](https://github.com/PhanCongVuDuc/Sonny/issues/new) with the `security` label. **Do NOT create a public issue** - use private communication instead.
+Please report security vulnerabilities by creating a [GitHub Issue](https://github.com/PhanCongVuDuc/Sonny/issues/new)
+with the `security` label. **Do NOT create a public issue** - use private communication instead.
 
 Include:
+
 - Type of issue
 - Affected source code location
 - Steps to reproduce