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

@rxreact/signal-connect

v1.0.2

Published

[![styled with prettier](https://img.shields.io/badge/styled_with-prettier-ff69b4.svg)](https://github.com/prettier/prettier) [![Greenkeeper badge](https://badges.greenkeeper.io/rxreact/signal-connect.svg)](https://greenkeeper.io/) [![Build Status](https:

Downloads

11

Readme

styled with prettier Greenkeeper badge Build Status Coverage Status

Development Sponsored By:
Carbon Five

Signal Connect

Connect your signal graphs to ReactJs Components!

Installation

In your project:

npm install @rxreact/signal-connect --save

or

yarn add @rxreact/signal-connect

RxJS and React are peer dependencies and need to be installed seperately

Usage

Define a signal graph using the @rxreact/signal library.

Here's lets use the example from that project's README of a Signal Graph to represent a login component and user authentication.

  const signalGraph = new SignalGraphBuilder<SignalsType, Dependencies>()
    .define(addPrimary('username$'))
    .define(
      addPrimary('password$'),
      addPrimary('submitButton$'),
      addDependency('api', api),
      addDerived('loginAttempts$', makeLoginAttempts, 'submitButton$', 'username$', 'password$'),
      addDerived('loginResponses$', makeLoginResponses, 'loginAttempts$', 'api'),
      addDerived('loginInProgress$', makeLoginInProgress, 'loginAttempts$', 'loginResponses$'),
      addDerived('loginSuccesses$', makeLoginSuccesses, 'loginResponses$'),
      addDerived('loginFailures$', makeLoginFailures, 'loginResponses$'),
      addDerived(
        'loginFailureMessage$',
        makeLoginFailureMessage,
        'loginAttempts$',
        'loginFailures$'
      ),
      addDerived('authStatus$', makeAuthStatus, 'loginSuccesses$')
    )
    .initializeWith({
      loginInProgress$: false,
      loginFailureMessage$: '',
      username$: '',
      password$: '',
      authStatus$: { status: 'unauthorized' }
    })
    .build()

Now, let's say we have a login form component:

const LoginForm: React.SFC<{
  loginInProgress: boolean
  loginFailureMessage: string
  username: string
  password: string
  submitButton: () => undefined
  usernameChanged: (username: string) => undefined
  passwordChanged: (password: string) => undefined
}> = ({
  loginInProgress,
  loginFailureMessage,
  username,
  password,
  submitButton,
  usernameChanged,
  passwordChanged
}) => {
  const onSubmit = (event: React.FormEvent<HTMLFormElement>) => {
    submitButton()
    event.preventDefault()
  }
  return (
    <form onSubmit={onSubmit}>
      <label htmlFor="username">User name:</label>
      <input
        type="text"
        id="username"
        name="username"
        value={username}
        disabled={loginInProgress}
        onChange={event => usernameChanged(event.target.value)}
      />
      <label htmlFor="password">Password:</label>
      <input
        type="text"
        id="password"
        name="password"
        value={password}
        disabled={loginInProgress}
        onChange={event => passwordChanged(event.target.value)}
      />
      <div>{loginFailureMessage}</div>
      <button disabled={loginInProgress} type="submit">
        Submit
      </button>
    </form>
  )
}

We want to connect the signals from our signal graph to props on this component. Here's where we use @rxreact/signal-connect. @rxreact/signal-connect exports a single function called connect:

import { connect } from '@rxreact/signal-connect'

connect behaves a lot like connect from react-redux, creating data props that get updated from the latest values in the graph, and functions as props that we can call to send data back to the graph. The simples use of connect looks like this:

const ConnectedComponent = connect(
  signalGraph,
  {
    loginInProgress: 'loginInProgress$',
    loginFailureMessage: 'loginFailureMessage$',
    username: 'username$',
    password: 'password$'
  },
  {
    usernameChanged: 'username$',
    passwordChanged: 'password$',
    submitButton: 'submitButton$'
  }
)(LoginForm)

The first object specifies data props that get updated as signals from the graph emit new values. (think mapStateToProps) The second objects specifies primary signals we use as entry points to send data back into the graph. In this case, the login form gets usernameChanged, passwordChanged, and submitButton as props. Each prop is a function, and when it's called (taking a signal parameter) it gets sent into the primary signals in the graph! (think mapDispatchToProps)

More Complex Usage

You may later want to have more control over assembling your props. In this case, you can can actually pass functions instead of objects, which get a single parameter than can be used to extract signals from the graph.

const ConnectedComponent = connect(
  signalGraph,
  outputs => ({
    loginInProgress: outputs('loginInProgress$'),
    loginFailureMessage: outputs('loginFailureMessage$'),
    username: outputs('username$'),
    password: outputs('password$')
  }),
  inputs => ({
    usernameChanged: inputs('username$'),
    passwordChanged: inputs('password$'),
    submitButton: inputs('submitButton$')
  })
)(LoginForm)

You also have access to an observable that represents the external props passed to the component in these functions:

const ConnectedProtectedAreaExtended = connect(
  authResourceGraph,
  (outputs, ownProps$: Observable<{ override: boolean }>) => {
    const authStatus$ = combineLatest(ownProps$, outputs('authStatus$')).pipe(
      map(
        ([{ override }, authStatus]): AuthStatus =>
          override ? { status: 'authorized', token: 'a token' } : authStatus
      )
    )
    const protectedResource$ = combineLatest(ownProps$, outputs('protected$')).pipe(
      map(
        ([{ override }, protectedResource]) =>
          override ? 'auth overridden' : protectedResource
      )
    )
    return {
      authStatus: authStatus$,
      protectedResource: protectedResource$
    }
  }

However, ideally you can use the simple version of connect in most cases, because signal graphs are flexible, and you can create many of your custom pieces/selections of data inside the graph itself!

Caveat Emptor

These libraries are still in development, use at your own risk

Enjoy!