gracehaz

4 ms·

1. 1.▲
   Introducing the Single Element Pattern(medium.freecodecamp.org)

   1 points by gracehaz 8y ago|0 comments
2. 2.▲
   Show HN: Single Element Pattern for React(github.com)

   2 points by gracehaz 8y ago|0 comments
3. 3.▲
   React's new context API: Toggle between local and global state(medium.freecodecamp.org)

   3 points by gracehaz 8y ago|0 comments
4. 4.▲
   React's new context API: Toggle between local and global state(medium.freecodecamp.org)

   2 points by gracehaz 8y ago|0 comments
5. 5.▲
   by gracehaz 9y ago

   This can be easily done by creating a npm script "generact path/to/boilerplate/component.js" and just running `npm run generact`. The difference though is that you'll still be prompted for component path and na
6. 6.▲
   by gracehaz 9y ago

   I'd done that too. But I found some problems with that approach: - you can't automatically create files (AFAIK); - it doesn't help your team mates, only works for you and with that specific editor; - if you start working on a
7. 7.▲
   by gracehaz 9y ago

   Kinda, but not really. XD It copies files, renames them and replaces their names in the contents.
8. 8.▲
   Show HN: Generate React components by replicating your own(github.com)

   38 points by gracehaz 9y ago|15 comments
9. 9.▲
   by gracehaz 9y ago

   Components relying on <State context> will be re-rendered with new state.
10. 10.▲
    Show HN: 2kB React state management library using the new Context API(github.com)

    10 points by gracehaz 9y ago|2 comments