Fix duplicate messages in install generator #1788
Conversation
Fixes duplicate success messages in Redux generator and duplicate NPM install output by preventing double execution of generator methods.
Walkthroughadd_js_dependencies now invokes a newly private install_js_dependencies and a Changes
Sequence Diagram(s)sequenceDiagram
autonumber
participant Dev as Developer
participant BG as BaseGenerator
Dev->>BG: add_js_dependencies
activate BG
BG->>BG: install_js_dependencies()
note right of BG #e6f7ff: private method — detects package manager and runs installer
BG-->>Dev: success/failure (boolean)
deactivate BG
sequenceDiagram
autonumber
participant User
participant IG as InstallGenerator
User->>IG: run_generators
activate IG
IG->>IG: prerequisite checks
IG->>IG: invoke generators
IG->>IG: add_bin_scripts
alt Redux disabled
IG->>IG: add_post_install_message
else Redux enabled
note right of IG #fff4e6: skipped — Redux provides its own message
end
deactivate IG
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Poem
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✨ Finishing touches
🧪 Generate unit tests
Tip 👮 Agentic pre-merge checks are now available in preview!Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.
Please see the documentation for more information. Example: reviews:
pre_merge_checks:
custom_checks:
- name: "Undocumented Breaking Changes"
mode: "warning"
instructions: |
Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).Please share your feedback with us on this Discord post. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Pull Request Review: Fix duplicate messages in install generatorThank you for this PR addressing the duplicate message issues in the install generator. I've conducted a thorough review covering code quality, potential bugs, performance, security, and test coverage. ✅ Code Quality and Best PracticesStrengths:
Suggestions:
🐛 Potential Bugs or IssuesIssue 1: Potential NPM Install Still Running Twice
This could lead to:
Recommendation: Either:
⚡ Performance ConsiderationsThe current implementation may cause performance issues:
Suggested Optimization: def add_js_dependencies
add_react_on_rails_package # Just add to package.json
add_react_dependencies # Just add to package.json
add_css_dependencies # Just add to package.json
add_dev_dependencies # Just add to package.json
install_js_dependencies # Single install at the end
end🔐 Security ConcernsNo security issues identified. The changes maintain proper:
🧪 Test CoverageCurrent Coverage:
Missing Test Coverage:
Recommended Additional Tests: it "calls npm/yarn install only once during installation" do
expect_any_instance_of(InstallGenerator).to receive(:run).with(/npm install|yarn install/).once
run_generator_test_with_args(%w[--redux], package_json: true)
end
it "does not show duplicate success messages with redux option" do
run_generator_test_with_args(%w[--redux], package_json: true)
output = GeneratorMessages.output.join("\n")
expect(output.scan("React on Rails Successfully Installed").count).to eq(1)
end📋 SummaryThe PR successfully addresses the duplicate message issue for Redux installations. However, there's still a concern about NPM install commands potentially running multiple times. I recommend:
The changes are safe to merge as-is for fixing the message duplication, but the NPM install duplication should be addressed in a follow-up PR if not resolved here. Great work identifying and fixing these generator issues! 🎉 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
lib/generators/react_on_rails/base_generator.rb (1)
233-233: Remove redundantprivate(fix RuboCop Lint/UselessAccessModifier)Remove the later
privatein lib/generators/react_on_rails/base_generator.rb (line 233). The earlierprivateis at line 106, so the second is redundant and triggers RuboCop. Runbundle exec rubocop -Ato confirm the pipeline is green.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
lib/generators/react_on_rails/base_generator.rb(1 hunks)lib/generators/react_on_rails/install_generator.rb(1 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
**/*.rb
📄 CodeRabbit inference engine (CLAUDE.md)
Use RuboCop for all Ruby code
Files:
lib/generators/react_on_rails/install_generator.rblib/generators/react_on_rails/base_generator.rb
lib/**/*.rb
📄 CodeRabbit inference engine (CLAUDE.md)
Place Ruby gem source under lib/ (e.g., lib/react_on_rails/*)
Files:
lib/generators/react_on_rails/install_generator.rblib/generators/react_on_rails/base_generator.rb
🪛 GitHub Actions: Lint JS and Ruby
lib/generators/react_on_rails/base_generator.rb
[error] 233-233: Command 'bundle exec rubocop' failed. Rubocop: Lint/UselessAccessModifier - Useless private access modifier. Offense at line 233. This offense is autocorrectable. Run 'bundle exec rubocop -a' to fix.
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (9)
- GitHub Check: dummy-app-integration-tests (3.4, 22)
- GitHub Check: dummy-app-integration-tests (3.2, 20)
- GitHub Check: examples (3.2, minimum)
- GitHub Check: examples (3.4, latest)
- GitHub Check: rspec-package-tests (3.2, latest)
- GitHub Check: claude-review
- GitHub Check: rspec-package-tests (3.4, minimum)
- GitHub Check: rspec-package-tests (3.4, latest)
- GitHub Check: rspec-package-tests (3.2, minimum)
🔇 Additional comments (2)
lib/generators/react_on_rails/install_generator.rb (1)
35-37: Good guard to prevent duplicate success messaging on Redux path.Conditionalizing
add_post_install_messagebehindoptions.redux?aligns with the PR goal and avoids double messages. LGTM.Please confirm that the Redux generator already emits a complete post‑install message so non‑Redux users aren’t missing guidance.
lib/generators/react_on_rails/base_generator.rb (1)
98-104: Centralize dependency installation — good consolidation.Calling
install_js_dependenciesfromadd_js_dependenciesshould stop the “second full npm install” and reduce noise. LGTM.Double‑check that no other top‑level generator still triggers a project‑wide install to avoid regressions (e.g., via
run "npm install"or similar).
…hods to proper private section
Code Review for PR #1788: Fix duplicate messages in install generator✅ Strengths
🔍 Observations & Suggestions1. Method visibility changeThe install_js_dependencies method was moved from public to private. While this is good encapsulation, verify that no external code relies on this method being public. The method is only called internally, so this change appears safe. 2. Test coverageThe existing tests in spec/react_on_rails/generators/install_generator_spec.rb verify that success messages appear correctly for both Redux and non-Redux installations (lines 66-86). However, consider adding explicit tests to verify:
3. Package manager detection logicThe package manager detection in install_js_dependencies (lines 197-207) is well-structured with proper fallback handling. The method correctly:
🔒 Security & Performance
✨ Code Quality
✅ Overall AssessmentThis is a well-executed bug fix that improves the user experience during installation. The changes are minimal, focused, and solve the reported issues effectively. The code maintains backward compatibility while fixing the duplicate message problems. Recommendation: Ready to merge after considering the test coverage suggestion above. |
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
lib/generators/react_on_rails/base_generator.rb (1)
196-223: Skip bulk install when direct installs already ran; add an early return guard.Avoids second install pass and duplicate logs when any fallback performed direct installs and nothing was queued via
add_npm_dependencies.Apply this diff:
def install_js_dependencies + # If fallbacks already installed packages directly and we didn't queue any + # package.json edits via `add_npm_dependencies`, skip the bulk install. + return true if @did_any_direct_install && !@used_add_npm_dependencies # Detect which package manager to use success = if File.exist?(File.join(destination_root, "yarn.lock")) run "yarn install" elsif File.exist?(File.join(destination_root, "pnpm-lock.yaml")) run "pnpm install" elsif File.exist?(File.join(destination_root, "package-lock.json")) || File.exist?(File.join(destination_root, "package.json")) # Use npm for package-lock.json or as default fallback run "npm install" else true # No package manager detected, skip end @@ success end
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
lib/generators/react_on_rails/base_generator.rb(3 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
**/*.rb
📄 CodeRabbit inference engine (CLAUDE.md)
Use RuboCop for all Ruby code
Files:
lib/generators/react_on_rails/base_generator.rb
lib/**/*.rb
📄 CodeRabbit inference engine (CLAUDE.md)
Place Ruby gem source under lib/ (e.g., lib/react_on_rails/*)
Files:
lib/generators/react_on_rails/base_generator.rb
🧠 Learnings (2)
📚 Learning: 2025-02-12T16:38:06.537Z
Learnt from: Romex91
PR: shakacode/react_on_rails#1697
File: package-scripts.yml:28-28
Timestamp: 2025-02-12T16:38:06.537Z
Learning: The file `node_package/lib/ReactOnRails.full.js` is autogenerated during the build process and should not be present in the repository.
Applied to files:
lib/generators/react_on_rails/base_generator.rb
📚 Learning: 2025-09-16T08:01:11.146Z
Learnt from: justin808
PR: shakacode/react_on_rails#1770
File: lib/generators/react_on_rails/templates/base/base/app/javascript/src/HelloWorld/ror_components/HelloWorld.client.jsx:2-2
Timestamp: 2025-09-16T08:01:11.146Z
Learning: React on Rails uses webpack CSS Modules configuration with namedExports: true, which requires the import syntax `import * as style from './file.module.css'` rather than the default export pattern. This configuration enables better tree shaking and bundle size optimization for CSS modules.
Applied to files:
lib/generators/react_on_rails/base_generator.rb
🧬 Code graph analysis (1)
lib/generators/react_on_rails/base_generator.rb (1)
lib/generators/react_on_rails/generator_messages.rb (1)
add_warning(13-15)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (9)
- GitHub Check: dummy-app-integration-tests (3.4, 22)
- GitHub Check: dummy-app-integration-tests (3.2, 20)
- GitHub Check: rspec-package-tests (3.4, minimum)
- GitHub Check: rspec-package-tests (3.2, minimum)
- GitHub Check: rspec-package-tests (3.2, latest)
- GitHub Check: rspec-package-tests (3.4, latest)
- GitHub Check: examples (3.4, latest)
- GitHub Check: examples (3.2, minimum)
- GitHub Check: build
🔇 Additional comments (1)
lib/generators/react_on_rails/base_generator.rb (1)
132-132: Approve — helpers privatized; public Thor tasks confirmedPrivate is correctly placed; the following methods remain public (Thor tasks): add_hello_world_route, create_react_directories, copy_base_files, copy_js_bundle_files, copy_webpack_config, copy_packer_config, add_base_gems_to_gemfile, add_js_dependencies, update_gitignore_for_auto_registration, append_to_spec_rails_helper
| install_js_dependencies | ||
| end |
There was a problem hiding this comment.
Duplicate installs still possible via fallbacks; gate bulk install and track fallbacks.
If add_npm_dependencies falls back to direct npm install inside any add_*_dependencies method, the final call to install_js_dependencies will run a second full install, reprinting output and wasting time. Track whether we used fallbacks vs. queued package.json edits, and skip the bulk install when appropriate.
Apply this diff to make the behavior single‑install:
@@
def add_react_on_rails_package
@@
- puts "Installing React on Rails package..."
- return if add_npm_dependencies(react_on_rails_pkg)
+ puts "Installing React on Rails package..."
+ if add_npm_dependencies(react_on_rails_pkg)
+ @used_add_npm_dependencies = true
+ return
+ end
puts "Using direct npm commands as fallback"
- success = run "npm install #{react_on_rails_pkg.join(' ')}"
+ success = run "npm install #{react_on_rails_pkg.join(' ')}"
+ @did_any_direct_install = true if success
handle_npm_failure("react-on-rails package", react_on_rails_pkg) unless success
end
@@
def add_react_dependencies
@@
- return if add_npm_dependencies(react_deps)
+ if add_npm_dependencies(react_deps)
+ @used_add_npm_dependencies = true
+ return
+ end
@@
- success = run "npm install #{react_deps.join(' ')}"
+ success = run "npm install #{react_deps.join(' ')}"
+ @did_any_direct_install = true if success
handle_npm_failure("React dependencies", react_deps) unless success
end
@@
def add_css_dependencies
@@
- return if add_npm_dependencies(css_deps)
+ if add_npm_dependencies(css_deps)
+ @used_add_npm_dependencies = true
+ return
+ end
@@
- success = run "npm install #{css_deps.join(' ')}"
+ success = run "npm install #{css_deps.join(' ')}"
+ @did_any_direct_install = true if success
handle_npm_failure("CSS dependencies", css_deps) unless success
end
@@
def add_dev_dependencies
@@
- return if add_npm_dependencies(dev_deps, dev: true)
+ if add_npm_dependencies(dev_deps, dev: true)
+ @used_add_npm_dependencies = true
+ return
+ end
@@
- success = run "npm install --save-dev #{dev_deps.join(' ')}"
+ success = run "npm install --save-dev #{dev_deps.join(' ')}"
+ @did_any_direct_install = true if success
handle_npm_failure("development dependencies", dev_deps, dev: true) unless success
endCommittable suggestion skipped: line range outside the PR's diff.
🤖 Prompt for AI Agents
In lib/generators/react_on_rails/base_generator.rb around lines 103-104, prevent
a second full JS install by tracking whether any add_*_dependencies method
performed a direct fallback install and skipping the final
install_js_dependencies when so; add an instance boolean (e.g. @used_fallbacks =
false) initialized in the generator, set it to true inside add_npm_dependencies
(and any other fallback branches) when you call npm/yarn directly, and only call
install_js_dependencies at the end if @used_fallbacks is false (so queued
package.json edits trigger the bulk install, but direct fallback installs do not
cause a second install).
Code Review for PR #1788: Fix duplicate messages in install generator✅ Overall AssessmentThis PR successfully addresses the duplicate message issues in the install generator. The changes are minimal, focused, and solve the problem effectively. 🎯 Code Quality & Best PracticesPositive aspects:
Suggestions:
🐛 Potential IssuesNone identified. The changes properly address the duplicate message problems without introducing new issues. ⚡ Performance Considerations
🔒 Security ConcernsNone. The changes don't introduce any security vulnerabilities. 🧪 Test CoverageConcern: While the existing tests at Recommendation: Consider adding a test that explicitly verifies:
Example test approach: specify "redux generator does not duplicate success messages" do
GeneratorMessages.clear
run_generator_test_with_args(%w[--redux], package_json: true)
output_text = GeneratorMessages.output.join("\n")
# Count occurrences of the success message
success_count = output_text.scan("🎉 React on Rails Successfully Installed!").length
expect(success_count).to eq(1)
end📝 Additional Notes
✅ ApprovalThis PR effectively fixes the reported issues with minimal, clean changes. The code quality is good and follows the project's conventions. I recommend approval with the minor suggestion to enhance test coverage for message deduplication verification. Great work on identifying and fixing these UX issues! 👍 |
Code Review for PR #1788: Fix duplicate messages in install generatorThank you for this PR addressing the duplicate message issues! I've reviewed the changes and here's my comprehensive feedback: ✅ Code Quality & Best PracticesStrengths:
Suggestions:
✅ Bug FixesThe PR successfully addresses both issues:
✅ Performance Considerations
✅ Security Assessment
|
Code Review✅ Strengths
🔍 Areas for Improvement1. Missing Test Coverage 🚨The PR checklist indicates tests were added/updated, but I don't see any new test files. Consider adding tests for:
2. Method Visibility InconsistencyIn
3. Potential Edge CaseThe condition 💡 Suggestions
describe "install generator messages" do
context "with redux option" do
it "does not display duplicate success messages" do
# Test implementation
end
end
context "without redux option" do
it "displays post-install message once" do
# Test implementation
end
end
end
def detect_package_manager
return :yarn if File.exist?(File.join(destination_root, "yarn.lock"))
return :pnpm if File.exist?(File.join(destination_root, "pnpm-lock.yaml"))
return :npm if File.exist?(File.join(destination_root, "package-lock.json")) ||
File.exist?(File.join(destination_root, "package.json"))
nil
end✅ Security & Performance
📝 DocumentationWhile the CHANGELOG update isn't required for this bug fix, consider adding a comment explaining why the post-install message is suppressed for Redux installations to help future maintainers understand the logic. VerdictThe changes effectively fix the duplicate message issues. However, test coverage should be added before merging to ensure the fixes work correctly and prevent regression. The code organization could be slightly improved for better maintainability. |
|
Code Review✅ Overall AssessmentThis PR successfully addresses the duplicate message issues in the install generator. The changes are clean and well-focused on the specific problems identified. 🎯 Code Quality & Best PracticesStrengths:
Suggestions:
🐛 Potential Issues
⚡ Performance Considerations
🔒 Security Concerns
🧪 Test Coverage
Recommendation: Add test cases to verify:
💡 Additional Suggestions
def detect_package_manager
return :yarn if File.exist?(File.join(destination_root, "yarn.lock"))
return :pnpm if File.exist?(File.join(destination_root, "pnpm-lock.yaml"))
return :npm if File.exist?(File.join(destination_root, "package-lock.json")) ||
File.exist?(File.join(destination_root, "package.json"))
nil
end
✅ ApprovalThe changes effectively fix the reported issues and the code is production-ready. The suggestions above are for future improvements and don't block merging. |
Code Review for PR #1788: Fix duplicate messages in install generatorSummaryThis PR addresses two duplicate message issues in the install generator:
✅ Strengths
🔍 Issues and Suggestions1. Unused Method in Redux Generator (Medium Priority)The add_redux_specific_messages method in react_with_redux_generator.rb:131 is defined but never called. This appears to be dead code that should either be:
Recommendation: Since this method clears existing messages and adds Redux-specific ones, it should probably be called after the Redux setup completes. Consider adding it to the generator workflow or removing it entirely. 2. Potential Race Condition (Low Priority)The install_js_dependencies method is now called within add_js_dependencies, which might run before all dependencies are fully written to package.json. Recommendation: Verify that all npm package additions complete before the install command runs. 3. Missing Test Coverage (Medium Priority)While the PR checklist indicates tests were added/updated, I don't see specific tests verifying:
Recommendation: Add specific test cases to verify the duplicate message fixes work as intended. 🔒 Security Considerations✅ No security concerns identified. The code properly validates package manager names before building commands, preventing command injection. 🎯 Performance Considerations✅ Positive impact: Eliminating duplicate npm install calls will reduce installation time, especially for projects with many dependencies. 📝 DocumentationThe inline comments added are helpful and explain the reasoning behind the conditional logic. 💡 Additional Suggestions
✅ Overall AssessmentThis PR successfully addresses the stated issues with minimal, focused changes. The refactoring improves code organization while fixing the duplicate message problems. With the suggested improvements (especially addressing the unused method and adding test coverage), this will be a solid contribution. Verdict: Approved with suggestions for improvement 👍 |
Code Review for PR #1788: Fix duplicate messages in install generatorSummaryThis PR addresses two duplicate message issues in the React on Rails install generator. The changes are well-structured and follow good software engineering practices. ✅ Strengths
🔍 Areas for Consideration
🚀 PerformanceThe changes improve performance by eliminating duplicate NPM install operations, which can save significant time during generator execution. 🔒 SecurityNo security concerns identified. Package manager detection and command execution follow safe patterns. ✅ Overall AssessmentThis is a solid bug fix that addresses the reported issues cleanly. The code quality is good and follows Rails generator conventions. With the addition of test coverage to prevent regression, this PR would be ready to merge. Recommendation: Approve with minor suggestions for test coverage enhancement. |
Code Review for PR #1788: Fix duplicate messages in install generatorThanks for this PR @ihabadham! I've conducted a thorough review of the changes. ✅ Strengths
🎯 Suggestions for Improvement
✅ Security & Performance
✅ Test CoverageThe existing test suite appears comprehensive with contexts for both 🔍 Verification NeededPlease verify that the Redux generator ( VerdictThe changes look good and effectively solve the duplicate message problem. With the minor documentation suggestion above, this PR is ready to merge. 👍 🤖 Generated with Claude Code |
Code Review for PR #1788: Fix duplicate messages in install generatorThank you for this PR! I've reviewed the changes and here's my feedback: ✅ What works well
🎯 Suggestions for improvement
✔️ No critical issues found
📊 Overall assessmentThis is a solid bug fix that addresses the reported issues cleanly. The changes are minimal and focused, which reduces the risk of introducing new issues. The code reorganization improves maintainability by grouping related functionality. Recommendation: ✅ Approve with minor suggestions The PR is ready to merge after considering the minor suggestions above, particularly around method visibility consistency. |
Code Review for PR #1788: Fix duplicate messages in install generatorThank you for this PR! I've reviewed the changes and here's my feedback: ✅ Strengths
🔍 Code Quality & Best PracticesThe code follows Rails generator conventions well. The refactoring in
|
Code Review for PR #1788: Fix duplicate messages in install generator🟢 Overall Assessment: APPROVEDThis PR effectively addresses the duplicate message issues in the install generator, with clean and minimal changes that solve the root causes. ✅ What I Like:
🎯 Code Quality & Best Practices:
🔒 Security Considerations:
⚡ Performance Impact:
🧪 Test Coverage Observations:The existing test suite covers:
Suggestion: Consider adding explicit test cases that verify:
💡 Minor Suggestions for Future Improvements:
✅ Conclusion:This is a well-crafted fix that addresses the reported issues without introducing complexity. The changes are minimal, focused, and maintain the existing architecture while solving the duplicate message problems effectively. Great work on keeping this fix clean and targeted! 👍 |
Code Review for PR #1788: Fix duplicate messages in install generator📋 SummaryThis PR addresses duplicate message issues in the install generator:
✅ Strengths
|
Code ReviewThank you for this PR fixing the duplicate message issues! Here's my comprehensive review: ✅ Strengths
🎯 Code Quality & Best Practices
|
Code Review for PR #1788: Fix duplicate messages in install generator🎯 SummaryThis PR successfully addresses the duplicate message issues in the install generator by:
✅ Strengths
🔍 Areas for Improvement
🐛 Potential Issues
🔒 SecurityNo security concerns identified. The code properly uses ⚡ PerformanceNo performance concerns. The changes actually improve performance slightly by eliminating redundant npm install calls. 📋 Recommendations
✨ Overall AssessmentApproved with suggestions ✅ This is a well-implemented fix that cleanly addresses the reported issues. The code is maintainable and follows Rails generator conventions. With the addition of specific test coverage for the deduplication behavior, this will be a solid improvement to the codebase. Great work on identifying and fixing this UX issue! The cleaner output will definitely improve the developer experience when setting up React on Rails. |
Code Review for PR #1788: Fix duplicate messages in install generator🎯 OverviewThis PR addresses two duplicate message issues in the install generator - duplicate Redux success messages and duplicate NPM install command execution. The changes are well-targeted and follow good refactoring practices. ✅ Strengths
🔍 Areas for Consideration1. Test CoverageWhile the existing tests at lines 167-176 in install_generator_spec.rb verify success messages appear, consider adding explicit tests to ensure:
Suggestion: Add a test that counts message occurrences to verify no duplicates occur. 2. Method OrganizationThe base_generator.rb now has install_js_dependencies as a private method alongside other dependency-related private methods. This organization is consistent and appropriate. 3. Error HandlingThe error handling in install_js_dependencies is appropriate - it warns but doesn't fail the generator if package installation fails, allowing users to manually install later. 🐛 Potential IssuesNone identified. The changes appropriately fix the reported issues without introducing new problems. 🔒 SecurityNo security concerns. The package manager detection and execution follows safe patterns without risk of command injection. 🚀 PerformanceMinor performance improvement by eliminating duplicate NPM install execution. 📝 DocumentationNo documentation updates needed as this is a bug fix that doesn't change the API or user-facing behavior. ✨ Suggestions for Future Improvements
✅ VerdictAPPROVED - This is a clean, focused fix that addresses the reported issues without introducing complexity. The code follows project conventions and maintains good separation of concerns. The changes correctly:
Great work on identifying and fixing these usability issues! 👍 |
Summary
Fixes two duplicate message issues in the install generator:
Pull Request checklist
Update documentationUpdate CHANGELOG fileThis change is
Summary by CodeRabbit