npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

ng-observable-input

v1.0.3

Published

Angular input properties as observable streams

Downloads

6

Readme

Installation

npm install -S observable-input

or

yarn add observable-input

Usage

import { Component, Input } from '@angular/core'
import { Observable } from 'rxjs/Observable'
import { ObservableInput } from 'observable-input'

@Component({
  templateUrl: './some-component.html',
  selector: 'app-some-component',
})
class SomeComponent {
  @Input() @ObservableInput()
  private index: Observable<number>

  @select()
  private selectedIndex: Observable<number>

  public isSelected = this.index.switchMap(
    index => this.selectedIndex.map(selectedIndex => selectedIndex === index)
  )
}

Then in some-component.html:

<span [class.selected]="isSelected | async">maybe selected</span>

Details

This decorator works by replacing the input with a property, the getter returns a value with type Observable<T> while the setter expects a variable of type T. This introduces a few drawbacks:

  • While you should generally only be reading your input values and not setting them, the mismatch of types for the setter and getter here is still potentially a source of confusion.
  • For now the angular code (whether AOT compiled or not) only writes to a component's inputs (in this case via the setter) and never reads from them, if it did it would receive a value with type Observable<T> when it expects a value of type T.
  • The angular compiler does not type check the values passed to a component match the types of the @Input, if it did it would raise an error indicating that the input should be of type Observable<T> instead of T.