[STORAGE][TYPES][BUGFIX] TaskEvent was incorrectly typed TaskState

[tkow]

close #2302

Summary

The type of storage task event is wrong.

Checklist

• Supports Android
• Supports iOS
• e2e tests added or updated in /tests/e2e/*
• Updated the documentation in the docs repo
  • LINK TO DOCS PR HERE
• Flow types updated
• Typescript types updated

Test Plan

Release Plan

[CATEGORY][type] [LOCATION] - Message

---

Think react-native-firebase is great? Please consider supporting the project with any of the below:

• 👉 Donate via Open Collective
• 👉 Follow React Native Firebase and Invertase on Twitter
• 👉 Star this repo on GitHub ⭐️
• 👉 Contribute; see our contributing guide

[mikehardy]

Wow, that looks pretty obvious - most type changes are backwards incompatible, but it seems like this could only have been used with a cast so I’d be shocked if this hurt people? I mean, I would probably still mark it v5.6 (using the updated “breaking change in minor” semver for v5.x.x) but this seems like it can only help. What do you think?

[mikehardy]

I just checked v6 and this looks fixed there, I don’t see a problem between the branches

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (v5.x.x@af32cc4). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             v5.x.x    #2303   +/-   ##
=========================================
  Coverage          ?   76.27%           
=========================================
  Files             ?       61           
  Lines             ?     1576           
  Branches          ?        0           
=========================================
  Hits              ?     1202           
  Misses            ?      374           
  Partials          ?        0

[mikehardy]

just read your thoughts on the linked issue, sounds good

let me think about how to release this, but I have no problem in general with a compatibility break if that’s what a fix like this so it’ll be either 5.5.5 or 5.6.0. Either way, thanks for the fix and I’ll merge it now, then you can depend on the commit hash or use patch-package with confidence it will converge with the next release

[tkow]

@mikehardy Sure. Thank you for that. This project's very amazingly nice for me and a lot of help us. I
have understood this project have tough work for migration to v6. I appreciate it.