Lit-rout NPM | npm.io

lit-rout

Please note: still a draft

Declarative, conditional rendering based on the Location for Lit applications.

Parts

A lit-rout custom component registered by the library
A custom component extended from lit-rout/RoutedLitComponent registered by the application

Check out https://www.npmjs.com/package/path-to-regexp#match about how to use route matching

Usage

HTML Template

<my-app>
  <lit-rout route="/">

    <!-- Custom Component that extends from lit-rout/RoutedLitElement -->
    <my-dashboard></my-dashboard>
    
    <!-- not a RoutedLitElement so updates for this are ignored -->
    <h3>I'm always rendered</h3>
    
  </lit-rout>

  <!-- nesting routes, "(.*)" signifies nesting. Required because routes are strictly matched -->
  <lit-rout route="/page(.*)">

    <my-page></my-page>
    
    <!-- nested route, will inherit all parent routes wihtout "(.*)" -->
    <lit-rout route="/:id">
      <my-page-with-route-params></my-page-with-route-params>
    </lit-rout>

  </lit-rout>
</my-app>

Custom RoutedLitElement

import { customElement } from 'lit/decorators';
import { RoutedLitElement } from 'lit-rout';

@customElement('my-dashboard')
export class MyDashboard extends RoutedLitElement<{}> {
  renderTemplate() {
    return html`<h2>Dashboard</h2`;
  }
}

@customElement('my-page')
export class MyPage extends RoutedLitElement<{}> {
  renderTemplate() {
    return html`<h2>Page</h2>`;
  }
}

@customElement('my-page-with-route-params')
export class MyPage extends RoutedLitElement<{ id: string }> {
  renderTemplate() {
    return html`<h2>Page ${this.params.id}</h2>`;
  }
}

About the components/API

Quick guide to the basic building blocks

`lit-rout` Custom Component

<lit-rout route="/path/to/success"><!-- content --></lit-rout>

A custom component registered by the library, with one attribute that should match (or not) the current URL.

This component will set the visible property on its child Elements. You will have to make sure that the child elements inherit from RoutedLitElement, otherwise they will be rendered at all times - match/update will ignore non-RoutedLitElements.

Can have multiple RoutedLitElements if needed.

`RoutedLitElement` Class

Just like a standard LitElement but:

(instead of the render method) you have to implement the renderTemplate method to return the HTML template,
class is generic, type is the interface/type describing the route params object

interface MyPageParams {
  id: string;
  title: string;
}

@customElement('my-page')
export class MyPage extends RoutedLitElement<MyPageParams> {
  renderTemplate() {
    const { id, title } = this.params // access the matched parameters from the URL - within the container lit-rout element !!!
    return html`<h2>My Page: ${name}/${id}</h2`;
  }
}

Please bear in mind that RoutedLitElements are always rendered, its their children that are de/attached (dis/connected) from the DOM so any lifecycle related logic should go into those components.