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

r-socs-core

v0.0.2

Published

R-SoCs core library

Downloads

12

Readme

r-socs-core

Separation of Concerns

What does the library do?

It makes instance methods of a subtree of React components available as injected props to a consumer component.

Why such a library?

To make separation of concern practical through composition easier than HoC.

How to use it?

Install the library

npm install --save r-socs-core

Import artefacts of the libary

import {
    Collector,
    withCollector,
    connect
} from 'r-socs-core';

Collect service component

See how to create a concrete Collector by extending the generic one in src/test-helpers/SimpleLogic/SimpleLogicCollector.js .

See an example of logic component which provides the methods to be collected in src/test-helpers/SimpleLogic/SimpleLogicComponent.js.

And see how to put Collector on the logic component to form a service in src/test-helpers/SimpleLogic/index.js.

Notes

    withCollector(LogicCollector)(LogicComponent);

provides a special instance function method this.hset through extension to the wrapped LogicComponent.

This instance function method should be used to generate the hset props needed to use child services, such as

    <Model {...props} hset={this.hset(name)} />

where the parameter name has the same meaning in connect(Logic, name) function.

Inject service props into consumer component

import { connect } from 'r-socs-core';

import SimpleLogic from '../test-helpers/SimpleLogic';

const NAME = 'NameOfService';
const ServicedComponent = connect(SimpleLogic, NAME)(TargetComponent);

Use injected props

Injected props are just normal props.

Dependnecy:

react > 16.8.4

Some basic optional conventions:

Service and Consumer artefacts naming convention

  1. A service component is named as XxxServiceComponent, XxxModelComponent or XxxLogicComponent.
  2. A "collected" service component is named as XxxService, XxxModel or XxxLogic.
  3. A consumer component may have any React component name.

Service and Consumer wrapper display names

  1. A "collected" service component is named as hCollect(XxxModelComponent).
  2. A "connected" service-consumer pair is named as hConnect(hCollect(XxxModelComponent)-TargetComponent).
  3. A "injecting" service-consumer pair is named as hInject(hCollect(XxxModelComponent)-TargetComponent).