lit / lit/lit.dev

[docs] Reactive Properties page never actually mentions how to pass properties to child components

Open
#1,147 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
142
Forks
230
PR merge metrics
No merged PRs in 30d

Description

### Feature Request
Add a pointer to the [Property Expressions](https://lit.dev/docs/templates/expressions/#property-expressions) section from the [Reactive Properties page](https://lit.dev/docs/components/properties/).

### Context
The [Reactive Properties page](https://lit.dev/docs/components/properties/) does a good job of explaining properties and state, but somehow never mentions explicitly how a Lit developer should pass a property to a child component.

It seems that information is found at the [Expressions page](https://lit.dev/docs/templates/expressions/) which is found in the "Templates" sub-section of the LHS nav, but this is not obvious (why should I know it's there?), and **searching for "properties" in the UI search element doesn't even return this page as a result**.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Reactive Properties page and the linked Property Expressions section to compare where property passing is currently explained. Add a pointer from the Reactive Properties page to Property Expressions, then verify that the page explicitly directs readers to the relevant guidance.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.