Wheel prototype UI

[antamy]

Initial concept of Wheel functionality

Work in progress

🤖 Generated with Claude Code

Co-Authored-By: Claude noreply@anthropic.com

[antamy]

@MarkT1065 bare bones right now, but I reached my session limit (2nd time today, idk if something changed). I'll pick this up again tomorrow, but wanted to share an initial look.

[MarkT1065]

so sayeth Claude ... I haven't pulled the branch and tried to run it yet.

PR #19: Wheel Prototype UI

  Status: OPEN | Changes: +7,726 lines, -1 line

  Summary: Working prototype of Wheel functionality with all specs from PR #18 plus implementation.

  Analysis:

  ✅ Strengths:

  1. Well-structured implementation:
    - Proper separation: model (wheel_prototype.go), handler (wheel_handlers.go), view (wheels.html)
    - Prototype data file (wheels_prototype.json) for testing
    - Route registration in server.go
    - Navigation updated to include wheels page
  2. Comprehensive documentation:
    - All 7 specs from PR #18 included
    - Additional "Enhance Commission Handling.md" specification (+1,403 lines)
    - Shows thoughtful planning
  3. Significant implementation effort:
    - 1,024 lines in UI template
    - 356 lines in handlers
    - 217 lines in model

  ⚠️ Critical Issues:

  Binary/Executable Files (Must Remove):
  - models.test.exe
  - stonks.exe
  - test.test.exe
  - wheeler.exe
  - data/Oldtest_db.db
  - data/myoptions.db

  Test/Debug Files (Should Remove):
  - test_output.log (+1,102 lines)
  - test_import.csv (+2 lines)
  - test_import_old.csv (+2 lines)

  📋 Recommendations:

  1. Immediate Actions:
    - Remove all .exe files and database files from PR #19
    - Remove test output logs and CSV files
    - Add/update .gitignore to prevent future commits of:
    *.exe
  *.db
  test_output.log
  test_import*.csv
  2. PR Strategy Options:
    - Option A: Close PR #18, clean up PR #19 (recommended)
    - Option B: Merge PR #18 first (specs only), then clean up and merge PR #19
    - Option C: Split PR #19 into specs + implementation PRs
  3. Before Merging PR #19:
    - Remove unwanted files
    - Verify prototype aligns with V2 spec Trade table design
    - Test the wheels UI functionality
    - Review commission handling enhancement

  Verdict: PR #19 shows solid work but needs cleanup before merge. The implementation approach is sound, but repository hygiene must be maintained.

[antamy]

My claude seemed to go a little off piste with this one. To be clear, it's not intended to be merged at all, I just PR'd it here to share early thinking. I haven't had time today to work on it, and I've also been looking at potential ways to conserve my tokens using an MCP.

[MarkT1065]

Before UI prototyping, my preference would be to make a solid data layer, which includes the schema, migrations/changes from existing, and solid tests covering all use cases. If all your scenarios can be expressed in data/test, then it'll work in a UI, too, and now we've got a test suite.

[antamy]

That's fine, I'm just using rapid prototyping to refine the scenarios that are in my head.