Add uniform baseplate option to Gridfinity calculator

[ntindle]

Description

Add "Prefer uniform baseplate sizes" toggle that allows users to optimize for uniform baseplate dimensions instead of mixed sizes. The feature intelligently
avoids creating impractical 1xN baseplates by enforcing a minimum size of 2x2 grids.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Performance improvement
• Code refactoring

Related Issue

Implements user request for uniform baseplate option

Changes Made

• Added preferUniformBaseplates setting to state management system
• Implemented smart calculateUniformBaseplates algorithm that:
  • Prioritizes fewer baseplate variants (1-3 types max)
  • Enforces minimum baseplate size of 2x2 grids (no 1xN pieces)
  • Accepts 85%+ coverage to avoid creating tiny edge pieces
• Added UI toggle in Bin Options section for the new preference
• Updated calculation logic to use uniform baseplates when enabled
• Added comprehensive test suite for uniform baseplate calculations

Testing

• All existing tests pass (194 tests passing)
• Added new tests for new functionality (7 new tests)
• Tested manually in browser
• Tested with different drawer dimensions
• Tested with custom printer settings
• Tested with half-size bins enabled/disabled

Test Results:

• 41.5" x 13.5" drawer: Successfully generates 10 × 5x4 uniform baseplates (vs 5 × 5x5 + 5 × 5x3 mixed)
• Odd dimensions: Correctly avoids 1xN pieces by accepting slight undercoverage
• Edge cases: All baseplates maintain minimum 2x2 size constraint

Screenshots

Feature adds a new toggle "Prefer uniform baseplate sizes" in the Bin Options panel

Checklist

• My code follows the project's code style guidelines
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have used unitMath service for all calculations (no native JS math operations)
• I have used @/ import paths consistently

[github-actions]

PR Quality Report 📊

Check	Status
TypeScript	✅
ESLint	✅
Tests	✅
Build	✅

View detailed results