Migration: Testing migration class to function component (Coordinates) about hajk HOT 2 OPEN

I tried using chatgpt and it managed to migrate this - pretty short - component:

from hajk.

So react is probably going to launch a compiler some time this year (according to some sources). This compiler will render some functions and hooks obsolete (useCallback, useMemo).

The current migration from class component to function component involves memoization via useMemo, like this:

 const coordinatesModel = useMemo(
    () =>
      new CoordinatesModel({
        map: props.map,
        app: props.app,
        options: props.options,
        localObserver: localObserver,
      }),
    [props.map, props.app, props.options, localObserver]
  );

This will not be neccesary when the compiler comes out. But for now, it is.

If we remove useMemo with the current state of react, the coordinatesModel will initialize on every render, which is not ideal.

So, the question is: do we migrate with "compiler-code" or not?

(Compiler code being without memoization)

If we migrate with "compiler-code", we might see some performance issuses due to unecceasry initializations until the compiler comes out.

If we migrate without "compiler-code", we might have to remove useMemo etc. later when the compiler comes out.

Thougts?

from hajk.