Tobiloba Adedeji

Oh! Interesting. 🤔🤔. So, it works now @manoharc1999?

> > Try upgrading to the latest beta, should work now possibly. Thanks for the patience so far @manoharc1999 > > Still not working in latest beta :( Oh, seriously??...

Let's see what @aidenybai thinks.

> > LGTM! Quick question, you are transforming the component directly to a block, right? > > Yes, that's correct 👍 @tobySolutions Ok, awesome!

> What if we could do something like this? > > ```jsx > const Block = block(function({ children }) { > return ... > }) > > bonk > ```...

> We currently use [compiler](https://github.com/aidenybai/million/blob/04975c3ccfb2592cfb32661cf220e0f8906ede8a/packages/compiler/react/transform.ts#L397) [warnings](https://github.com/aidenybai/million/blob/04975c3ccfb2592cfb32661cf220e0f8906ede8a/packages/compiler/react/transform.ts#L561) to mark deoptimizations / limitations. What if we created a ESLint plugin for better developing experience? This will be a life-saver!!

Nope, there isn't. Go on ahead and take it @adetoye-dev!

Go ahead @ehizman!

I think it's safe to close this now @aidenybai. You have merged @Drex72's issue, right?

Hmm, not sure @nojiritakeshi. I mean, for is a component that is made for optimized array rendering. Not sure, how this ties in with what it does 🤔🤔🤔