Cannot access state/hooks from local methods about flutter_hooks HOT 10 CLOSED

Oh, that kind of access. I thought you talked about ancestorStateOfExactType, my bad.

With hooks you shouldn't use methods, and instead inline functions inside the build method:

class Foo extends HookWidget {
  @override
  Widget build(BuildContext context) {
    final counter = useState(0);

    void incrementCounter() {
       counter.value++;
    }

    return RaisedButton(
      onPresssed: incrementCounter,
      child: Text(counter.value.toString()),
    );
  }
}

from flutter_hooks.

Oh, that kind of access. I thought you talked about ancestorStateOfExactType, my bad.

With hooks you shouldn't use methods, and instead inline functions inside the build method:

class Foo extends HookWidget {
  @override
  Widget build(BuildContext context) {
    final counter = useState(0);

    void incrementCounter() {
       counter.value++;
    }

    return RaisedButton(
      onPresssed: incrementCounter,
      child: Text(counter.value.toString()),
    );
  }
}

If we create our methods within the build method in Flutter, will it not impact performance because the method will be recreated every time the build method is called?

from flutter_hooks.

This is generally considered a bad practice to access the State class. It is an implementation detail.

Instead you should explicitly expose the desired values through an Inheritedwidget (provider package?) or constructors.

from flutter_hooks.

Sorry for the late reply, but I don't follow what you mean that is bad practise to "access the state".

When using "flutter create" to setup a new project, the _MyHomePageState has a method called _incrementCounter that modifies the state of the widget. Is this bad practise?

Using a HookWidget, should methods on this object never be able to modify its own state ?

from flutter_hooks.

Ahh, ofc. Makes sense. Dont know why I didnt think of that.

Thanks for helping out!

from flutter_hooks.

This reinforces the idea that a class is a bit pointless with hooks.

If you haven't already, I encourage you to give functional_widget a try!

from flutter_hooks.

I will check it out, thx

from flutter_hooks.

Hitting this issue myself, but figured the only way around it is to have functions, vars, etc defined within the build method.
Got an example of the functional_widget you mention?

from flutter_hooks.

figured the only way around it is to have functions, vars, etc defined within the build method.

That's expected. Do that.

from flutter_hooks.

Oh, that kind of access. I thought you talked about ancestorStateOfExactType, my bad.
With hooks you shouldn't use methods, and instead inline functions inside the build method:

class Foo extends HookWidget {
  @override
  Widget build(BuildContext context) {
    final counter = useState(0);

    void incrementCounter() {
       counter.value++;
    }

    return RaisedButton(
      onPresssed: incrementCounter,
      child: Text(counter.value.toString()),
    );
  }
}

If we create our methods within the build method in Flutter, will it not impact performance because the method will be recreated every time the build method is called?

I saw a similar SO question and the answers unanimously said it's a bad practice.

from flutter_hooks.