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

sn-controls-react

v1.0.1-beta.1

Published

React controls for sensenet ECM

Downloads

85

Readme

sn-controls-react

Greenkeeper badge Join the chat at https://gitter.im/SenseNet/sn-controls-react License Commitizen friendly

Collection of React components for sensenet ECM with React Materialize

Sense/Net Services

Usage and installation

You can install the latest version from NPM

npm install --save sn-controls-react

You can import fieldcontrol and viewcontrol components into your React App the conventional way.


import { NewView, EditView, CommandButtons } 'sn-controls-react';

...

View Controls

View Controls are almost the same as the .ascx Content Views in sensenet Webpages. This components define how the given Content will be rendered. As a Content is built up of Fields the View Control displays the Content using Field Controls to provide a surface to display/modify the Field values of the Content. View Control therefore depends on the Content Type of the specific Content.

Content creation form (NewView)

import { NewView } from 'sn-controls-react'
import createBrowserHistory from 'history/createBrowserHistory'
const history = createBrowserHistory()

// content: Content | required  | empty Content Object
// history: history Object made with createBrowserHistory() | optional | called after submit | default: window.history.back()
// onSubmit: Function | optional | called on submit event | default: window.history.back()

<NewView 
content={content} 
history={history} 
onSubmit={() => {})} />

Content editor form (EditView)

import { EditView } from 'sn-controls-react'
import createBrowserHistory from 'history/createBrowserHistory'
const history = createBrowserHistory()

// content: Content | required  | empty Content Object
// history: history Object made with createBrowserHistory() | optional | called after submit | default: window.history.back()
// onSubmit: Function | optional | called on submit event | default: window.history.back()

<EditView 
content={content} 
history={history} 
onSubmit={() => {})} />

Content browse view (BrowseView)

import { BrowseView } from 'sn-controls-react'

// content: Content | required  | empty Content Object

<BrowseView 
content={content} />

Field Controls

Just as legacy controls in sensenet Webpages Field Control components provide GUI for setting/modifying Field values of a Content but this time not as .ascx views but React Components.