Remove submodules

[AustinChangLinksys]

User description

• Remove submodules dependency
• Include Privacy-Widget as a remote library

---

PR Type

Other

---

Description

• Remove Git submodules configuration

• Switch Privacy-Widget to remote dependency

• Update pubspec.yaml with Git URL reference

---

Diagram Walkthrough

flowchart LR
  A["Git Submodules"] -- "remove" --> B["Remote Git Dependency"]
  C["Local Plugin Path"] -- "replace with" --> D["Git URL Reference"]

Loading

File Walkthrough

	Relevant files
Configuration changes	.gitmodules Remove submodule configuration                                                      .gitmodules Remove entire submodule configuration for Privacy-Widget plugin +0/-3      widgets Remove subproject reference                                                            plugins/widgets Delete subproject commit reference +0/-1
Dependencies	pubspec.yaml Switch to remote Git dependency                                                    pubspec.yaml Replace local path dependency with Git URL Add specific version reference (v1.2.6) +3/-1

---

[qodo-code-review]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Dependency Pinning Using a Git dependency pinned to tag v1.2.6 may affect reproducibility and update flow; verify the tag exists, the commit is immutable, and that this version is compatible with current code and transitive dependencies. privacygui_widgets: git: url: https://github.com/linksys/PrivacyGUI-Widgets.git ref: v1.2.6 Source Integrity Ensure the Git URL points to the correct repository and that builds work in CI/CD without Git credentials; consider adding a commit hash for stricter integrity if needed. git: url: https://github.com/linksys/PrivacyGUI-Widgets.git ref: v1.2.6 Platform/Build Impact Switching from a local path to a remote Git package can change plugin resolution; verify iOS/Android platform builds, plugin registration, and any asset/plugin configurations previously sourced from the submodule. privacygui_widgets: git: url: https://github.com/linksys/PrivacyGUI-Widgets.git ref: v1.2.6 flutter_blue_plus: ^1.4.0

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	✅ Pin dependency to a specific commit Suggestion Impact: The ref for privacygui_widgets was changed from tag v1.2.6 to the specific commit b945f41f67dadd1d30fc06dd4e9d40caddba03c2. code diff: privacygui_widgets: git: url: https://github.com/linksys/PrivacyGUI-Widgets.git - ref: v1.2.6 + ref: b945f41f67dadd1d30fc06dd4e9d40caddba03c2 Pin the privacygui_widgets dependency to the specific commit hash from the old submodule (b945f41f67dadd1d30fc06dd4e9d40caddba03c2) instead of the tag v1.2.6 to ensure build reproducibility. pubspec.yaml [65-68] privacygui_widgets: git: url: https://github.com/linksys/PrivacyGUI-Widgets.git - ref: v1.2.6 + ref: b945f41f67dadd1d30fc06dd4e9d40caddba03c2 [Suggestion processed] Suggestion importance[1-10]: 8 __ Why: The suggestion correctly identifies that pinning a dependency to a commit hash instead of a tag is a best practice for ensuring build reproducibility and stability, which is a significant improvement.	Medium
Possible issue	Commit refreshed lockfile pin Run flutter pub get and commit the updated pubspec.lock file to pin the exact dependency revision, ensuring reproducible builds for all developers and CI. pubspec.yaml [65-68] +# pubspec.yaml remains unchanged; ensure pubspec.lock is refreshed and committed privacygui_widgets: git: url: https://github.com/linksys/PrivacyGUI-Widgets.git ref: v1.2.6 [Suggestion processed] Suggestion importance[1-10]: 7 __ Why: The suggestion highlights the crucial best practice of updating and committing the pubspec.lock file to ensure reproducible builds, which is highly relevant to the dependency change in the PR.	Medium
No more code suggestions