webc/lit-class-fields

Dlaczego

Lit makes each reactive property an accessor on the prototype. A class field with the same name (open = false) creates an own property on every instance that hides that accessor, so assigning this.open = true changes the value but never schedules a render: the component looks frozen and no error is shown.

Poprawka

In JavaScript, set initial values in the constructor after super(): this.open = false. With decorators in JavaScript, use accessor (@property() accessor open = false). In TypeScript, set useDefineForClassFields: false in tsconfig.json, or use declare or accessor on the field.

Przykłady

// bad
static properties = { open: { type: Boolean } }
open = false
// good
static properties = { open: { type: Boolean } }
constructor() {
  super()
  this.open = false
}

Źródła

• Lit, Reactive properties (avoiding issues with class fields)

Przeczytaj w terminalu

npx github:dawidolko/frontend-skills explain webc/lit-class-fields