MAJOR FINDING: Latest hyperscript version has NO 3 def statement limit! Test Results (tests/mjs/9-hyperscript-def-limit.test.mjs): ✅ 1 def statement - PASS ✅ 2 def statements - PASS ✅ 3 def statements - PASS ✅ 4 def statements - PASS (beyond historical limit) ✅ 5 def statements - PASS (well beyond limit) Changes: 1. Created comprehensive def limit test - tests/mjs/9-hyperscript-def-limit.test.mjs - Tests 1, 2, 3, 4, 5 def statements - Verifies both parsing and function execution - Provides detailed analysis and recommendations 2. Updated PROJECT-MEMORY.md - Section 2: Changed from "NEEDS RETESTING" to "REMOVED IN LATEST VERSION" - Documented test findings and historical context - Added migration plan for hyperscript file organization - Updated test count to 10 systematic tests 3. Updated doc/HYPERSCRIPT-RULES.md - Rule 2: Removed 3 def limit warning - Documented historical context (Hyperscript 0.9.12 had limit) - New best practice: Organize by category in separate files - Added recommended file structure Impact: - Can now use unlimited def statements in hyperscript - Enables cleaner architecture with category-based organization - Allows migration from cv-functions.js back to hyperscript - Better alignment with hypermedia/server-driven pattern Next Steps: - Create organized hyperscript file structure - Migrate toggle functions from JavaScript to hyperscript - Migrate hover sync functions to hyperscript - Test each migration thoroughly
4.5 KiB
Hyperscript Development Rules
MANDATORY RULES - ALWAYS FOLLOW
Rule 1: Code Cleanliness
More than 3 lines of hyperscript → Move to function in file
- Inline hyperscript in HTML should be kept minimal (≤3 lines)
- Longer logic MUST be extracted to named functions in ._hs files
- HTML templates should be clean and readable
Rule 2: File Structure - Organized by Category
✅ NO def statement limit with latest hyperscript!
HISTORICAL NOTE (2025-11-17): Hyperscript 0.9.12 had a 3 def limit. Latest version REMOVED this limitation.
- Test verification:
tests/mjs/9-hyperscript-def-limit.test.mjs(all 5 def statements passed) - Migration in progress: Moving functions from JavaScript back to hyperscript
Current Best Practice: Organize hyperscript functions by category in separate files
static/hyperscript/
├── toggles._hs # Toggle functions (CV length, icons, theme)
├── hover-sync._hs # Hover synchronization functions
├── utils._hs # Utility functions (print, scroll, etc.)
└── keyboard._hs # Keyboard shortcut handlers
Benefits of Hyperscript Organization:
- ✅ Clean separation of concerns
- ✅ Easy to locate and maintain functions
- ✅ No artificial limitations
- ✅ Server-side hypermedia pattern (functions loaded with HTML)
- ✅ Still callable from anywhere using
call functionName(args)
Rule 3: HTML Structure Cleanliness
HTML must be as clean as possible regarding hyperscript
✅ GOOD - Clean, readable:
<input type="checkbox"
id="lengthToggle"
_="on change call toggleCVLength(my.checked)">
❌ BAD - Inline logic nightmare:
<input type="checkbox"
id="lengthToggle"
_="on change
if my.checked
remove .cv-short from .cv-paper
add .cv-long to .cv-paper
set localStorage['cv-length'] to 'long'
set #lengthToggleMenu's checked to true
else
remove .cv-long from .cv-paper
add .cv-short to .cv-paper
set localStorage['cv-length'] to 'short'
set #lengthToggleMenu's checked to false
end">
File Organization
static/hyperscript/
├── functions._hs → Core utilities (3 defs max)
├── toggles._hs → Toggle functions (3 defs max)
└── hover._hs → Hover sync functions (3 defs max)
Load Order in templates/index.html:
<script type="text/hyperscript" src="/static/hyperscript/functions._hs"></script>
<script type="text/hyperscript" src="/static/hyperscript/toggles._hs"></script>
<script type="text/hyperscript" src="/static/hyperscript/hover._hs"></script>
<script src="https://unpkg.com/hyperscript.org@0.9.12"></script>
Required Functions
Core Functions (functions._hs)
printFriendly()- Handle print-friendly viewinitScrollBehavior()- Initialize scroll variableshandleScroll()- Manage scroll behavior and fixed button positioning
Toggle Functions (toggles._hs)
toggleCVLength(isLong)- Switch between short/long CVtoggleIcons(showIcons)- Show/hide iconstoggleTheme(isClean)- Switch between default/clean theme
Hover Sync Functions (hover._hs)
syncPdfHover(show)- Sync hover state across PDF buttonssyncPrintHover(show)- Sync hover state across print buttonshighlightZoomControl(show)- Highlight zoom control on hover
Why These Rules Exist
Maintainability
- Functions with descriptive names are self-documenting
- Easier to test and debug
- Changes in one place instead of scattered across templates
Performance
- Browser caches ._hs files
- Reduces HTML payload size
- Cleaner separation of concerns
Hyperscript 0.9.12 Limitation
- Parser breaks with >3
defin single file - MUST split into multiple files
- Each file: ≤3
defstatements
Common Mistakes to Avoid
❌ DON'T: Put all functions in one file if you have >3 defs ❌ DON'T: Write long inline hyperscript in HTML ❌ DON'T: Delete functions to work around the 3-def limit
✅ DO: Split functions across multiple ._hs files ✅ DO: Keep HTML clean with function calls ✅ DO: Maintain all required functions for clean architecture
Testing After Changes
- Check browser console for parse errors
- Verify all functions are defined (no "X is null" errors)
- Test all toggles work correctly
- Hard refresh browser (Ctrl+Shift+R) to clear cache
Last Updated: 2025-01-17 Hyperscript Version: 0.9.12 Status: MANDATORY - ALWAYS FOLLOW