Giter Club home page Giter Club logo

sn-controls-react's Introduction

sn-controls-react


This package is not under active development. You can find our latest packages in the sensenset/sn-client monorepo.


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

Collection of React components for sensenet ECM with Material-UI

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.

sn-controls-react's People

Contributors

gallayl avatar gitter-badger avatar gkatai avatar greenkeeper[bot] avatar herflis avatar

Stargazers

 avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

Forkers

gitter-badger

sn-controls-react's Issues

An in-range update of material-ui-pickers is breaking the build 🚨

The dependency material-ui-pickers was updated from 1.0.0-rc.17 to 1.0.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

material-ui-pickers is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Edit and browse view in React

@borsi commented on Wed Apr 05 2017

For starters, create the Edit and Browse view for the Task content type

Acceptance criteria

  • The field control templates which are needed for us to create an edit form for a task are ready
  • Task fields are editable
  • Also implemented in the React-redux example todo app
    Nfrs: npm, github repo, codecov, codacy, travis

@borsi commented on Tue May 23 2017

Field controls

  • Display Name: Has own control named "Display Name".
  • Name: Has own control: "Name".
  • Start date & Due date: DateTime type fields. The client is responsible for the UTC time format conversions to and from local time. (Can be set to show just the date or the whole date time)
  • Assigned to: Reference field. Needs an own control specific to the User content type (it should inherit from the Reference grid control).
  • Priority: Choice field, dropdown list.
  • Status: Ditto.
  • Completion: Number control - should be unified all over the place (we don't need currency or percentage controls, it should be derived from a parameter)
  • Description: Wysiwyg editor.
  • Modified by: Read-only reference field.
  • Modification Date: DateTime field.
  • Version: Read-only Choice field. (we may not need to display it)
  • Index: Numer field - plain integer.
  • buttons (save and cancel - not field controls)

An in-range update of react is breaking the build 🚨

There have been updates to the react monorepo:

    • The devDependency react was updated from 16.6.1 to 16.6.2.
  • The devDependency react-dom was updated from 16.6.1 to 16.6.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the react group definition.

react is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of @types/react is breaking the build 🚨

The devDependency @types/react was updated from 16.7.0 to 16.7.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/react is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Assigned to: Reference field on task content type

  • Assigned to: Reference field. Needs an own control specific to the User content type (it should inherit from the Reference grid control).

Controls over reference field

  • Reference grid - the legacy grid is not very flexible -- without the picker it is not complete

  • Tags input autocomplete reference field
    • Tags should be able to support templating

DMS MVP - Login

As an end user I want to be able to log in to my document management system mvp page, so I can try out the features of the app.

Acceptance criteria:

  • The user can log in when she provides her e-mail addres and password (and registered before)
  • We are validating the e-mail format client-side
  • Both fields are validated as required
  • If either of the provided information is wrong (or the user is not registered), we display a "Wrong user name or password" error message.
  • When the user clicks (or taps) on the login button, we disable it until the end of the evaluation. If the login is successful, the user finds herself at the DMS front page.

initial wireframe:
login

An in-range update of @sensenet/client-core is breaking the build 🚨

The dependency @sensenet/client-core was updated from 1.3.0 to 1.3.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@sensenet/client-core is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Document management MVP

Create an mvp based on the hypothesis that our customers would like to see stronger, better, and faster document management features to be able to decide if they want to use sensenet.

Hypothesis:

We think that part of our user group consists of enterprise people who are searching for Document management solutions. Our mvp is out to test this assumption by showing the smallest valuable subset of sensenet's document management capabilities.

We'll measure:

  • The number of users arriving on the platform
  • The number of users registering
  • The number of returning users by weekly cohorts
  • The top features requested by the users
  • User feedbacks about the product and the features via surveys
    • via direct feedback
    • via github issues

When do we finish the experiment?

  • After one month, check:
    • When the number of arriving users is insufficient
    • When users arrive, but they do not register
    • When the experiment is considered successful and a product can be finalized for release

Tasks

  • Determine the release process
  • Create the communication process for every release (what to post where, how to communicate)
  • Build the measurement system and test it before starting the experiment
  • Build the mvp, duh
  • During the process of the learning, communicate what we've learned and why we decided to go which way.
  • After the experiment, communicate everything we learned

Must have Use cases

  • Show Folders and documents in a list
  • Create new folders and documents
  • Upload new folders and documents from the menu
  • Upload new folders and documents by dragging and dropping them
  • Rename Folders and documents
  • Organize folders and documents
    • Move a document in a folder by changing it's path
    • Move a document in a folder by drag and dropping it
    • Move a folder similarly
    • Copy ~ (and rename or overwrite automatically, if a document with the same name exists)
  • Delete documents
  • Delete multiple documents
  • Delete folders containing multiple documents or nothing
  • Edit word, excel (or ppt?) files by double clicking on them

An in-range update of material-ui-pickers is breaking the build 🚨

The dependency material-ui-pickers was updated from 1.0.0 to 1.0.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

material-ui-pickers is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v1.0.1

Thanks for 3 contributors that made this release possible

Here are some highlights ✨:

  • Fix missing tslib dependency
  • Fix common typescript errors
  • Improve bundle size by removing prop types and treeshakable classes

Fixes

  • Fix missing tslib de
  • Fix a bug with white border if localized dialog actions are too wide
  • Fix not updating component on initialFocusedDate change
FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of @types/node is breaking the build 🚨

The devDependency @types/node was updated from 10.12.8 to 10.12.9.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Update Material to @latest

  • Update/clear dependencies (especially scoped packages) and fix related issues
  • Update tslint config and fix related issues
  • Remove Materialize
  • Install latest official material-ui
  • Fix thingz
  • Update TodoApp
  • Update DMS Demo

An in-range update of react-quill is breaking the build 🚨

The dependency react-quill was updated from 1.3.2 to 1.3.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

react-quill is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 1 commits.

  • 80c8271 Lock down @types/quill version (#420)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

  • Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

  • engines was only updated if it defined a single version, not a range.
  • .nvmrc was updated to Node.js 10
  • .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖


FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of @types/react is breaking the build 🚨

Version 16.4.14 of @types/react was just published.

Branch Build failing 🚨
Dependency @types/react
Current Version 16.4.13
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

@types/react is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

DMS MVP - Lazy Registration

As an end user, I want to be able to register on the Sensenet7 - Document management mvp site.

Bugs:

  • When successfully registering, I sometimes cannot go back to the register tab.

Acceptance crit:

  • The user needs to provide a valid e-mail address
  • The correct format is signified with a placeholder
  • The user also needs to provide her password in password fields - twice.
  • The password needs to be longer than 8 characters, needs to contain numbers, capitals and special characters The password can be anything longer than 3 characters. This is a demo.
  • The user gets a relevant error message on the form, when the format is not valid
  • In addition to the client-side validation, we - obviously - validate on the server side as well
  • When the user clicks on the Register button, it becomes disabled so she can only submit her registration once
  • A loader-spinner signifies the loading, when we create the users' content
  • One e-mail can only be used once
  • When the registration is successful, the user gets to the login page, where she can log in.
  • There is a recaptcha on the register form that prevents bots from registering
  • In the future we'd like to store more data about the user
  • The user is informed about our cookie policy and privacy policy

Tracking:

  • A custom event is fired, when the user submits the form.
  • send a notification about every registration?

ToDo

Talk about

  • One e-mail address
  • Registration API

Notes

Url structure:

  • home: dms.demo.sensenet.com/
  • registration: dms.demo.sensenet.com/registration
  • login: dms.demo.sensenet.com/login
  • profile: dms.demo.sensenet.com/profile

[edit: added initial wf]
register

An in-range update of @types/react is breaking the build 🚨

The devDependency @types/react was updated from 16.7.7 to 16.7.8.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/react is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of material-ui is breaking the build 🚨

There have been updates to the material-ui monorepo:

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the material-ui group definition.

material-ui is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.