issue 28 refactor issue 59 linear layout - #63
Conversation
martin-raden
left a comment
There was a problem hiding this comment.
looks nice! I reviewed all changes and agree with them. They nicely generalize redundant code parts, as I had hope for...
There are a few things to change, see review below.
I will play around with the UI to test a few border cases and to ensure the UI behaviour is still the same. Will report if I find anything, but given the changes I reviewed, I dont expect much to come.. most code was kept unchanged!
thanks a lot!
Best,
Martin
martin-raden
left a comment
There was a problem hiding this comment.
here the request for the RRI-linearization issue
|
Issue #28 refactoring reportThis report records behavior-preserving cleanup completed for Issue #28. Removed code
Structural changes
Remaining architectural candidatesThe clone audit still identifies repeated static markup when HTML is included: parallel Compatibility and verificationThe camel-case field IDs and URL parameter names finalized before this refactor |
…s://github.com/BackofenLab/vaRRI-js into codex/issue-28-refactor-issue-59-linear-layout
|
Review follow-up completed in ee72f3d. All inline requests are addressed and answered: local development loads src/vaRRI.js while the Pages artifact uses dist/vaRRI.min.js; the refactoring report lives in the PR discussion rather than the repository; the diagnostic now runs once before the complete test suite; and linear rail spacing uses the larger loop with documentation and regression coverage. The separate request for the second example is also implemented: wu-2024 enables both forceLayout and forceLayoutLinear, protected by a UI regression test. Verification: 4 suites and 283 tests passed, and the production Pages minification/path rewrite was reproduced successfully. No renderer behavior was removed in this follow-up. |
fix #28
fix #59