plusnew

This Framework is built, because we believe that having typesafety and good debuggability is key. Why another framework? Because plusnew puts the Developer-Expierence first, and cares strongly about maintanability.

Plusnew keeps the magic as little as possible, and puts explicity first. E.G. when you write a line of code which changes the state, the dom will change immediately. This is important for predictability and testability.

Component

Components in plusnew just need a name and a render-function. The render-function gets called when a new instance of that component is created.

When props from the parent or stores are changing, the render-function does not get called again. But only a subset that you can define with a closure.

Component-Types

Function-Factory

import plusnew, { component, Props } from '@plusnew/core';

type props = { value: string };

export default component(
  // ComponentName for debuggability enhancements
  'ComponentName',
  // The render-function which gets called at initialisation
  // and gets a Observer-Component which delivers the properties from the parent
  (Props: Props<props>) =>
      <>
        <span>some static content</span>
        <Props>{props =>
          // in props.value is the value you got from your parent-component
          // this render-function gets called each time when the parent gives you new properties
          <div>{props.value}</div>
        }</Props>
      </>
);

Class

import plusnew, { Component, Props } from '@plusnew/core';

type props = { value: string };

export default class AppComponent extends Component<props> {
  // ComponentName for debuggability enhancements
  static displayName: 'ComponentName';
  // The render-function which gets called at initialisation
  // and gets a Observer-Component which delivers the properties from the parent
  render(Props: Props<props>) {
    return (
      <>
        <span>some static content</span>
        <Props>{props =>
          // in props.value is the value you got from your parent-component
          // this render-function gets called each time when the parent gives you new properties
          <div>{props.value}</div>
        }</Props>
      </>
    );
  }
}

Props

The props-values aren't given to you directly, but as an "observer-component".

This component expects a render-function as a child. This function will be called each time a prop changes. This way you have more control of what will be selected for rerendering.

Stores

Stores are used to persist your state and inform the components when the state changed. They consist of the initialStateValue and a reducer function.

The reducer function gets called, when a new action gets dispatched. This reducer gets the current state of the store and the action which just got dispatched. The new state will be the reducers return value.

The reducer function is optional. When it is not set, the dispatched value will be the new state of the store.

Each store has an Observer-Component, which expects a render-function as a child. This render-function gets called whenever a store changes it's state.

import plusnew, { component, store } from '@plusnew/core';

const INITIAL_COUNTER_VALUE = 0;

export default component(
  'ComponentName',
  () => {
    const counter = store(INITIAL_COUNTER_VALUE, (previousState, action: number) => previousState + action);

    return (
      <div>
        <button
          onclick={(evt) => {
            evt.currentTarget; // Typescript knows that this element is a HTMLButtonElement, because of context
            counter.dispatch(1)
           }}
        />
        <button
          onclick={(evt) => counter.dispatch(2)}
        />
        <counter.Observer>{state =>
          // This function is the only part which gets executed on a state change
          <div>{state}</div>
        }</counter.Observer>
      </div>
    );
  },
);

Context

Context is a way to provide data for nested components, without passing everything by props.

The Provider is the container who stores the state. A Consumer is a way to get the data and to dispatch a new reducer action.

import plusnew, { component, context } from '@plusnew/core';

const INITIAL_COUNTER_VALUE = 0;

const counterContext = context<number, number>();

const ContainerComponent = component(
  'ComponentName',
  () => {
    const counterStore = store(INITIAL_COUNTER_VALUE, (previousState, action: number) => previousState + action)

    return (
      <counterStore.Observer>{counterState =>
        <counterContext.Provider state={counterState} dispatch={counterStore.dispatch}>
          <NestedComponent />
        </counterContext.Provider>
      }</counterStore.Observer>
    );
  }
);

const NestedComponent = component(
  'ComponentName',
  (Props, componentInstance) =>
    <counterContext.Consumer>{(state, dispatch) =>
      <div>
        <button
          onclick={(evt) => {
            dispatch(1)
          }}
        />
        <button
          onclick={(evt) => dispatch(2)}
        />
        {state}
      </div>
    }</counterContext.Consumer>
  );
);

Helper-Components

Portal

With portals you can render elements outside of your normal tree, whereever you want. PortalExit is where all the stuff you have in PortalEntrance will land.

import plusnew, { component, PortalExit, PortalEntrance } from '@plusnew/core';

export default component(
  'ComponentName',
  () =>
    <>
      <div>
        <PortalExit name="portalName"/>
      </div>
      <div>
        <PortalEntrance name="portalName"><span /></PortalEntrance>
      </div>
    </>,
);

ElementLifecycle

The ElementLifecycle-Component can take care of dom-elements which were mounted and of dom-elements to be unmounted. When a dom-element gets created the according elementDidMount or elementWillUnmount gets called, with the dom-element as a parameter.

Same goes for dom-elements which will get unmounted. Simply return a resolved Promise when the animation is done and you want the dom-element to actually be deleted.

Note: Dom-Elements inside Dom-Elements will not trigger the callbacks, only the most outer dom-elements will trigger the callback.

import plusnew, { component, store } from '@plusnew/core';
import { ElementLifecycle } from '@plusnew/driver-dom';

export default component(
  'ComponentName',
  () => {
    const show = store(true);

    return (
      <ElementLifecycle
        elementDidMount={(element) => {
          // For example you can call the Element.animate function
          // https://developer.mozilla.org/en-US/docs/Web/API/Element/animate
          element.animate([{ opacity: '0' }, { opacity: '1' }], { duration: 3000 })
        }}
        elementWillUnmount={(element) => {
          // either return undefined, to delete the element immediately or a promise
          // e.g. https://developer.mozilla.org/en-US/docs/Web/API/Animation/finished
          return element.animate([{ opacity: '1' }, { opacity:  '0' }], { duration: 3000 }).finished;
        }}
      >
        <show.Observer>{state =>
          // When this button gets created it calls the elementDidMount
          // when it gets deleted the elementWillUnmount gets called beforehand 
          state === true && <button onclick={() => show.dispatch(false)}>Remove me :)</button>
        }</show.Observer>
      </ElementLifecycle>
    );
  },
);

Async

The Async-Component is used for displaying asynchronous content. Return as a promise, and it will show the loading content, until the promise got resolved.

For example, you can implement that a dom element gets created after a period of time, or you can lazyload another module and display it when it got loaded. The given Promise should get resolved with an JSX-Element you want to show.

import plusnew, { component, Async } from '@plusnew/core';


export default component(
  'ComponentName',
  () =>
    <Async
      pendingIndicator={<span>Loading asynchronously a module</span>}
      constructor={() => import('path/to/lazy/module')} // This function will only be called once, if you want to call it another time than destroy the Async-Component with a different key property
    >
      {module => // The given parameter is the value of your resolved promise
        <module.default />
      }
    </Async>
);

Idle

This component is for displaying expensive but lowpriority content. The children of this component will be displayed when the browser is in idle or the application is signaling that it is urgent now.

import plusnew, { component } from '@plusnew/core';
import { Idle } from '@plusnew/dom';
import ExpensiveComponent from './ExpensiveComponent';

export default component(
  'ComponentName',
  () =>
    <Idle urgent={false}>
      <ExpensiveComponent /> {/* component will not be displayed immediately */}
    </Idle>,
);

Try

The Try-Component is for handling errors. When an error occured in the render function, the catch-function will be executed and the return value will be displayed. Be aware that every subcomponent of a try-component catches all exceptions in the render functions.

import plusnew, { component, Try } from '@plusnew/core';

export default component(
  'ComponentName',
  () =>
    <Try
      catch={() => <span>Error happened</span>}
    >
      {() => throw new Error('something unexpected happened')}
    </Try>
);

Mounting Application

import plusnew, { component, Try } from '@plusnew/core';
import driver from '@plusnew/driver';
import MainComponent from './MainComponent';

/*
  First parameter is the Component which you want to be rendered,
  Second parameter are the renderOptions, with which you can modify the behaviour of the whole application
*/
plusnew.render(<MainComponent />, {
  driver: driver(document.body) // the driver function needs to know where the root is gonna be 
});