[TBD] Make statusbar mutations obvious

[dmtrKovalenko]

Reason

The main reason for this issue is that now it's really not obvious that status-bar mutates the state. For me, before I started maintaining this project, this module looks like a View rendering on top of everything other, with the position absolute. And that wasn't really clear that there is no state, but only mutations.

That can really lead the bugs. I want to make it more clear, that there is no rendering at all in the StatusBar component. Only mutation in the lifecycle hooks. And currently, codebase is a bit smells as from my point of view.

Solution

I am thinking about getting rid of the component at all. Just provide the hook.

useStatusBarMutation({ hidden: true, animation: "fade" )}

This will internally use useEffect and will not make additional calling to the native module, as static methods right now.

P.S.: This is open to discussion, want to know what @cpojer thinking about that.

[thymikee]

I'm supportive to that. I'd just make sure to:

1. Introduce hooks next to legacy component API
2. produce a warning that the component is going away in the next major version so please migrate to hooks or imperative module calling (with links to migration guide)
3. Remove component in a major version bump

[krizzu]

Happy to see that change, same as you, found it confusing to use it as a component.

[dmtrKovalenko]

Will work on that!

[Marcello168]

@thanks