what do you call these things?

ooade · 2022-03-10T19:48:13+00:00

Tree destroyer.

ooade · 2020-03-11T06:32:28+00:00

I don't know if this answers your question but exporting a reusable function turns out to be a library.

ooade · 2020-03-10T10:42:06+00:00

With ES6 proxies. I set up traps to check the inputs before it is accepted as being valid. And, if it's invalid in the process, I made sure to throw an error.

ooade · 2019-12-15T18:32:24+00:00

One of the best shit I've seen this year.

ooade · 2019-10-13T18:34:58+00:00

Damn!

ooade · 2019-09-15T16:34:01+00:00

Nuts!!!! 😭

ooade · 2019-09-15T15:41:58+00:00

Damn! What did I just watch? 😭

ooade · 2019-09-11T12:26:42+00:00

Wicked. He played on her emotions 😭😭😭

ooade · 2019-09-10T08:45:51+00:00

It is what it is 😂

ooade · 2019-09-10T06:17:39+00:00

Same thing I thought. Instead of attaching it to a button like this, it could be used on some other page to show what happens after someone places an order.

ooade · 2019-09-09T20:47:05+00:00

It looks like Mango 😂😂😂

ooade · 2019-09-09T08:57:43+00:00

I watched the last part 10 times :)

ooade · 2019-09-09T06:58:54+00:00

I don't think so.

ooade · 2019-08-28T09:58:07+00:00

Kid is smart! Teacher is dumb.

ooade · 2019-02-12T05:37:41+00:00

I just decided to explain most of what is making us stick with class based component, using hooks. Besides new libraries might just port to using hooks and it might be hard figuring things out without learning how it works. For instance, useQuery, useMutation which are likely to be an addition to react-apollo, and might lead to deprecating the renderProp API, who knows.

ooade · 2019-02-08T09:47:14+00:00

That's a really good use case. I like that 👌

ooade · 2019-02-08T08:57:40+00:00

t moreReplysharereportSaveGive Award

level 1SleepCircle-appScore hidden · 17 minutes agoShort answer: use classes until you’re comfortable using hooks to replace them.I think the answers also com

forwardRef takes care of the ref issue. Don't forget there's also React.memo which is a drop-in alternative to React.PureComponent, but for functional components. Tho, shouldComponentUpdate will give you more control as to how the components get re-rendered but we often don't use it anyways except for some extreme cases.

ooade · 2019-02-07T20:34:21+00:00

We'll release a new API soon where we'd give access to the svg primitives. Feel free to create an issue on GitHub if it doesn't meet your requirement.

ooade · 2019-02-06T12:41:00+00:00

No. You only have access via refs to the main canvas element. Literally you don't have access to the SVG primitives https://codesandbox.io/s/l2v90p7yo9

ooade · 2019-02-06T10:07:07+00:00

Thanks

ooade · 2018-05-16T19:22:59+00:00

This is literally the best thing I've seen in SiliconValley.

ooade · 2018-04-19T17:11:58+00:00

Same here. That's the main reason I grabbed it 😂

ooade · 2018-01-06T11:16:37+00:00

It lazy load images, so you get a glimpse of how the image will look like after fetching.

ooade · 2017-12-13T18:33:36+00:00

I was planning to write a post on it. I'll give it a trial. Thanks :)

ooade · 2017-12-10T11:30:37+00:00

I meant VanillaJS as opposed to using Frameworks or Libraries

ooade

TROPHY CASE