webcomponent: let user to define what are attribute vs props or both via useMetadata
Open
enhancement
web-components
- Dominant language
- TypeScript
- Stars
- 14.4k
- Forks
- 672
- PR merge metrics
- No merged PRs in 30d
Description
We should let the user overwrite what are attribute vs props or both with useMetadata
Contributor guide
Research direction
Start by locating the webcomponent output handling and the useMetadata entry point in the TypeScript compiler. Trace how attributes and props are currently determined, then clarify the intended metadata shape and precedence for attributes, props, or both. Done means webcomponent generation respects those user-defined choices with coverage for each mode.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100