Skip to content

Fix typing for custom elements with dot notation#307

Closed
ThatsEmbarrassing wants to merge 1 commit intoTroyAlford:developfrom
ThatsEmbarrassing:fix/dot-notation-typing
Closed

Fix typing for custom elements with dot notation#307
ThatsEmbarrassing wants to merge 1 commit intoTroyAlford:developfrom
ThatsEmbarrassing:fix/dot-notation-typing

Conversation

@ThatsEmbarrassing
Copy link

See: #306

@ThatsEmbarrassing ThatsEmbarrassing changed the title fix: typing for custom elements with dot notation Fix typing for custom elements with dot notation Sep 14, 2025
@TroyAlford
Copy link
Owner

Hi @ThatsEmbarrassing — thanks for the contribution! I'm going to merge this change in along with some others as part of #308

@TroyAlford TroyAlford closed this Sep 19, 2025
TroyAlford added a commit that referenced this pull request Sep 19, 2025
…ng (#308)

## Summary

Refactors TypeScript typings for the `components` prop to support nested component collections and adds support for additional unary operations.

## What Changed

- **Type Safety**: Added `ComponentType` and `ComponentsType` definitions for better component collection support
- **Unary Operations**: Added bitwise NOT (`~`) and `typeof` operator support
- **Error Handling**: Fixed error handling logic to prevent execution on parse errors
- **Developer Experience**: Improved IntelliSense and autocomplete for complex component hierarchies

## Why

- Better type safety when passing nested component collections
- More complete JavaScript expression evaluation
- Cleaner, more maintainable type definitions
- More robust error handling

Closes #297
Closes #304
Closes #305
Closes #306
Closes #307
@TroyAlford
Copy link
Owner

This is now out/available in v2.4.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants