react-talend-components

A set of stateless components which follows the Talend Guidelines

[![NPM][npm-icon] ][npm-url]

[![Travis CI][travis-ci-image] ][travis-ci-url]
[![Quality][quality-badge] ][quality-url]
[![dependencies][dependencies-image] ][dependencies-url]
[![devdependencies][devdependencies-image] ][devdependencies-url]
[![peerdependencies][peerdependencies-image] ][peerdependencies-url]

[npm-icon]: https://nodei.co/npm/react-talend-components.svg?downloads=true
[npm-url]: https://npmjs.org/package/react-talend-components
[travis-ci-image]: https://travis-ci.org/Talend/react-talend-components.svg?branch=master
[travis-ci-url]: https://travis-ci.org/Talend/react-talend-components

[dependencies-image]: https://david-dm.org/Talend/react-talend-components.svg
[dependencies-url]: https://david-dm.org/Talend/react-talend-components
[devdependencies-image]: https://david-dm.org/Talend/react-talend-components/dev-status.svg
[devdependencies-url]: https://david-dm.org/Talend/react-talend-components#info=devDependencies
[peerdependencies-image]: https://david-dm.org/Talend/react-talend-components/peer-status.svg
[peerdependencies-url]: https://david-dm.org/Talend/react-talend-components?type=peer

[quality-badge]: http://npm.packagequality.com/shield/react-talend-components.svg
[quality-url]: http://packagequality.com/#?package=react-talend-components

Conventions

Please look at our CONTRIBUTING first.

Please read our style guidelines first.

Supported browsers

Thanks to BrowserStack for providing real browser testing infrastructure.

$3

All components are created using the yeoman talend generator using stateless option.

yo talend:react-component
> (nature) stateless
> (tests) snapshot

$3

We want to avoid {children} as much as possible.
We believe an app should only pass arguments to stateless components.

So please don't do Pull Requests (PR) to add {children} on leaf components.

But what is a leaf component ?
It's a component that is not supposed to contain another component.
For example the following components are leaf components:

* AppHeaderBar
* SidePanel
* List
* Breadcrumb
* Icon
* Action(s)

But the following are not leaf:

* Layout

If you feel the need to add {children} this means we have forget a use case.
In this case please expose your use case and try to see how
it could be done by passing some props.

$3

The API we have for all components is the following for an event handler

``javascript
const onClick(event, payload) {
//do what ever you want
}
return
`

$3

Our tests are using the react-test-renderer aka snapshot testing.
This is by far the best tool to test pure components.

For the documentation and developpement environnement
we are using React StoryBook.

`shell
npm start
`

$3

If you want to create a link
please use Action component which accept a link prop.

Anchor need href. We are in a single page application, so JavaScript
decides the behavior, not the browser.
So we don't want to see any anchor link in the markup.

If you want to use Button from react-bootstrap don't forget
to add the role + bsStyle="link".

`javascript
const model = {id: ...};
const onClick(event, payload) {
//do what ever you want
payload.action.label === 'click me';
payload.model === model;
};
label="click me"
icon="svg-yeah"
onClick={onClick}
model={model}
/>
`

$3

We all are used to `` but this is finished now.
We are using `` because with this one we are able
to support svg icons which is on the way to be our next gen icons sets.

If you want you can register an new Icon this way:

`javascript
Icon.register('svg-test', ());
`

$3

open screenshots.config.json file.

The top of the file should stay unchanged.
The stories are registred this way:

`javascript
"Action": {
"default": [
{
"name": "action-default",
"selector": ["#default", "#hidelabel"]
}
]
},
``

Action* is the string name of 'storiesOf(' call
default* is the exact string of the .add / .addWithInfo call
* the content is an array of Object with name + selector
name* will be the name of the screenshot(s)
selector is a string or an array of string which is behind used to call document.querySelect(selector*) so you can try your selector.

npm scripts

* npm start -> launch storybook on localhost:6006
* npm run prepublish -> build the sources into the lib folder
* npm test -> to execute unit test
* npm run lint -> check the code style
* npm run watch -> watch the source to trigger a build

LICENSE

Copyright (c) 2006-2016 Talend

Licensed under the Apache V2 License