About _textEditingController

[busslina]

Is there any particular reason to use memo instead value here?:

TextEditingController _textEditingController(
  WidgetSideEffectRegistrar use, {
  String? initialText,
}) {
  final controller = use.memo(() => TextEditingController(text: initialText));
  use.effect(() => controller.dispose, [controller]);
  return controller;
}

I'm just about start implementing a ReArch port to Dart ReAct and I just want to use the best tools in the best way.

[busslina]

I just started it, but don't know when I will finish it. Any advice or contribution is welcome. I hope that it won't be "extremely hard" for me haha.

https://github.com/busslina/rearch-dart/tree/introducing-react-rearch/packages/react_rearch

[busslina]

Okay, gonna see...

[...] includes all that functions (component lifecycle + setstate + ...)

[busslina]

Done. Gonna test it: https://github.com/busslina/rearch-dart/blob/introducing-react-rearch/packages/react_rearch/lib/src/widgets/consumer.dart

[busslina]

Yessss, seems working. It has to contain any bug somewhere hehe.

I will test it more migrating a small/medium project.

[busslina]

https://github.com/busslina/rearch-dart/tree/introducing-react-rearch/packages/react_rearch/example

[GregoryConrad]

Pretty neat!

[GregoryConrad]

The reason for memo over value here is mostly style, but memo is often used in situations like this when the value it returns could change in the future. In the text editing controller example, it won't since initialText is irrelevant after it has been created, but it many other situations a change to the initialText (or whatever the constructor parameter may be) would warrant recreating the object.