I've found myself using a React Stateless component but with support for onClick handlers and have seen a lot of examples circulate around with the same syntax as well. Here's an example.

Thoughts on adding support for something like this? And what do you think about naming?

The biggest difference between this and _rsc (Related #12) is it's wrapped in a return block with support for functions or logic above the return statement.

import React from 'react';

const Cat = ({name}) => {
    const handleClick = () => {
        console.log(`meow from ${name}`);
    };
    return (
        <div onClick={handleClick}>{name}</div>
    );
}

Cat.propTypes = {
    name: React.PropTypes.string
};

export default Cat;

Any plans to add the following snippets?

class TodoItem extends React.Component {
   // ...
}

and

constructor(props) {
    super(props)
    // ...
}

_cdm => <_cdm></_cdm>

wtf?

Hi,

I was wondering if I can make a pr that changes
import React from 'react'
to
import React, {PropTypes} from 'react'

as it save writing React. before each prop we want to validate

React Router release v2.0 and changed a lot of the API, these snippets need to be updated to match the new API.

I will get to this at some point, but wouldn't mind a PR if someone really needs this now.

Hi!

I want to add some RN snippets. How could I proceed?

i was a huge fan and used this snippets everywhere. but recently i switched to flow type javascript. and no snippets shows up then.

If _cpt is meant to represent Class.propTypes = { ... }, it should instead of:

.PropTypes = {
  : React.PropTypes.string
}},

look like this:

.propTypes = {
  : React.PropTypes.string
};

Shouldn't it?

wiki page for react-snippets looks to be outpf date with with the actual code.

The div tags for the following snippets are created as <div/> which is not valid html syntax:

• _cer
• _rcc
• _ren

Hey dude, should we use:

example: '''
  foo() {
    // code
  }
'''

Or:

example: "foo() {\n\t//code\n\t}"

I was wondering if you want a default version because you rewrote my last PR,

🎉

Is it possible that we disable the forced use of "use strict";?

Many thanks for this very useful plugin, I still find it useful (despite it bugs me with that use strict thing).

Thanks!

Is there anyway for this package to support .jsx files? It currently looks like it only supports .js files.

FYI - I disabled this package because it interferes with React Atom package (https://atom.io/packages/react). I'm unable to use the functionality of React (atom package) when atom-react-snippets is enabled.

Hi,

As we have React: Class.propTypes = { ... } - _cpt, why not adding, for example, React: Class.defaultProps = { ... } - _cdp for defaultProps?

Currently there is only React: getDefaultProps() { return {...} } - _gdp which can not works with class MyComposent extends React.Component {

React 17 does not rely on
import React from 'react';
anymore.

Tried to modify "atom-react-snippets/snippets/React (JSX).cson" but after adding a snippet the whole package stopped working. Even an uninstall an reinstall did not resolve the issue.

Is there a way to add a configuration for your snippets to allow including semicolon, where the default option is not to have it?

If you think it makes sense, I can write a PR for that.

Hi, the _cer snippet seems not working. when I type cer the menu does not pop up, other snippets work fine.

I was looking for a snippet that would give me just a quick skeleton for a stateless React component. As I mainly use these for composition, they don't have PropTypes. So I was happy to see that there's a _rsc and _rscp to differentiate between stateless components with and without PropTypes. But unfortunately, both snippets contain the same content, i.e. they both generate a PropType skeleton. Why is this so?