rhales 0.3.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 9e468b139c203a063276ccd0f890b0b7439a7c4459a96f132ed1e53c01623b11
+  data.tar.gz: 786e0f95fa3d592b5451f7538d350f558f31545eb99973f5384bbde2fd474a99
+SHA512:
+  metadata.gz: fd02c37df3e02b5e423eeb7a1929ca2393a98ee0c6569724256846cd168ffa5476e4d94e18cbd9fc28149d0f50ff957423fbd1c165fe0e30f83d281e6075ab04
+  data.tar.gz: 8b9f7d88831a6e78ae811a56a4fe0c95e1c8962011ebbbcb7927e4cfb6dbcde798f66e4a2998fb89fcf30f356c7d2ca3134548971b3721331aacad6f90e501d5

data/CLAUDE.locale.txt

@@ -0,0 +1,7 @@
+Our own private local claude notes. Not read by claude or checked in.
+
+https://claudelog.com/mechanics/plan-mode
+https://handlebars-lang.github.io/spec/#sec-handlebars-specification-statements
+https://github.com/jeremyevans/rodauth/tree/588b865cf70c7f327f0f24a4e277dfe787a6674f/doc
+https://docs.anthropic.com/en/docs/claude-code/hooks#subagentstop
+https://www.anthropic.com/engineering/claude-code-best-practices

data/CLAUDE.md

@@ -0,0 +1,90 @@
+# Feature Implementation Guidelines
+
+## Common Commands
+- Use bin/rackup to run the dev server
+- bundle exec rspec spec/rhales/: Run test suite for current changes
+- gem build rhales.gemspec: Build the gem
+- bundle exec rspec spec/rhales/ --format documentation: Run tests with verbose output
+- rake rhales:test: Run Rhales-specific tests
+- rake rhales:validate: Validate template files
+- git worktree add ../feature-name feature-branch: Create parallel workspace
+- gh issue view [number]: Review GitHub issue details
+- gh pr create: Create pull request with context-aware commit message
+
+## Workflow: Feature Implementation
+
+### 1. Research & Planning Phase
+IMPORTANT: Always research and plan before coding. Use "think" or "think hard" for complex features.
+
+- Read relevant files and documentation WITHOUT writing code yet
+- Understand the two-layer data system (app, props)
+- Review adapter interfaces and dependency injection patterns
+- Create implementation plan in markdown file or GitHub issue
+- Document security implications and edge cases
+
+### 2. Implementation Phase
+Follow test-driven development when possible:
+
+1. Write RSpec tests first (mark with "TDD - no implementation yet")
+2. Confirm tests fail appropriately
+3. Commit tests
+4. Implement code to pass tests WITHOUT modifying tests
+5. Ensure no global state dependencies (OT.conf references)
+6. Verify HTML escaping and security measures
+7. Commit implementation
+
+### 3. Validation & Review
+- Run full test suite: `bundle exec rspec spec/rhales/`
+- Check for any global configuration usage
+- Update README.md and CHANGELOG.md with changes
+- Verify YARD documentation is complete
+- Use `gh` to create descriptive pull request
+- Address review comments in separate commits
+
+## Code Style
+- CRITICAL: Make MINIMAL changes to existing patterns
+- Preserve existing naming conventions and file organization
+- Use existing utility functions - avoid duplication
+- Use dependency injection over global state
+- Maintain adapter interface compliance
+- Keep context objects immutable
+- Ensure proper HTML escaping in templates
+
+## Multi-Task Guidelines
+For complex features requiring parallel work:
+- Use git worktrees for independent components
+- Keep adapter changes separate from core changes
+- Use /clear between unrelated tasks to optimize context
+- Document progress in CHANGELOG.md
+
+## Project-Specific Notes
+
+### Core Components to Consider
+- **Configuration**: Block-based configuration with validation
+- **Context**: Three-layer system with dot-notation access
+- **Parsers**: Two manual recursive descent parsers, for .rue files and handlebars templates
+- **Parser**: .rue file parsing with manual recursive descent
+- **Rhales**: Handlebars-style template engine
+- **Hydrator**: Client-side data injection with CSP support
+- **Adapters**: Pluggable auth and session interfaces
+
+
+### Key File Locations
+- **Core Logic**: `lib/rhales/`
+- **Main Entry Point**: `lib/rhales.rb`
+- **Unit & Integration Tests**: `spec/rhales/`
+- **Gem Specification**: `rhales.gemspec`
+- **Rake Tasks**: `Rakefile`
+
+### Key Patterns
+- **Template Syntax**: Uses Handlebars-style syntax (e.g., `{{variable}}`, `{{#if condition}}...{{/if}}`, `{{> partial_name}}`)
+- **Data Hydration**: Uses a `<data>` block in `.rue` files to define a JSON object for client-side hydration, which supports variable interpolation
+- **Security**: Default HTML escaping, CSP nonce support for scripts, and CSRF token handling are built-in
+- **Configuration**: All configuration is handled via an injected `Configuration` object, avoiding global state
+
+### Testing Patterns
+- Mock adapters for auth/session testing
+- Use fixtures in `spec/fixtures/templates/`
+- Test all three context layers independently
+- Verify template caching behavior
+- Check false/nil handling explicitly

data/LICENSE.txt

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2024-2025 Delano Mandelbaum
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.