Repository navigation
v1.2.0 - Complete Diagnostic and Parser Fixes
π Major Business Logic Fixes
Fixed Core Parsing Issues
- β Correct view.tree parsing: Only tabs for indentation, proper property detection
- β Fixed getCurrentComponent: Now correctly finds nested components by cursor position
- β Enhanced component tracking: Properties correctly assigned to their respective components
- β Improved project scanning: Components properly added to project on file open
Fixed Diagnostic Issues
- β No more false 'Component not found': Components defined in same document are recognized
- β No more false 'Duplicate property': Properties in different components no longer flagged as duplicates
- β
Fixed operator validation:
<=and<=>operators correctly distinguished - β Removed built-in filtering: All components now shown in autocomplete (user requested)
Parser Logic Improvements
- β Nested component support: Parser correctly handles component hierarchy
- β
Binding operator detection: Proper parsing of
<=,<=>, and=>operators - β Property scope resolution: Properties correctly associated with their containing components
- β Tab-only indentation: Enforces view.tree standard (tabs only, no spaces)
Completion & Navigation
- β All project components: Shows ALL components found in project (no filtering)
- β Better context detection: Improved logic for component_name, property_name, etc.
- β Enhanced definition resolution: Correct file path resolution (.tree β .ts/.css.ts)
π§ Implementation Details
- Updated
parseViewTreeFileto follow review recommendations - Fixed component stack tracking for nested components
- Improved
handleDidOpento update project scanner before validation - Enhanced property-to-component relationship mapping
- Streamlined binding validation regex patterns
π Testing
- All existing tests pass
- Added tests for nested component parsing
- Enhanced component validation tests
- Verified on real project files
This release addresses all major diagnostic false positives and parsing issues reported in the review.