Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix type of RemoteMessage data property #3172

Merged
merged 1 commit into from
Feb 5, 2020

Conversation

ziyaddin
Copy link
Contributor

@ziyaddin ziyaddin commented Feb 5, 2020

Fixes #3129

Summary

See description of #3129.

Checklist

  • Supports Android
  • Supports iOS
  • e2e tests added or updated in packages/**/e2e
  • Flow types updated
  • Typescript types updated

Test Plan

Release Plan

[TYPES] [ENHANCEMENT] [MESSAGING] - Change RemoteMessage.data property type from Object to { [key: string]: string }.


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

@claassistantio
Copy link

claassistantio commented Feb 5, 2020

CLA assistant check
All committers have signed the CLA.

@mikehardy
Copy link
Collaborator

@ziyaddin thanks! - this seems fine to me based on inspection and previous discussion - do you have it running locally and it works for you? I use typescript myself and remote messages so I'll end up checking it too, but the more verification in the old/stable branch the better

@mikehardy mikehardy added Workflow: Waiting for User Response Blocked waiting for user response. plugin: messaging FCM only - ( messaging() ) - do not use for Notifications tools: typings TypeScript / Flow Version: 5.x.x labels Feb 5, 2020
@ziyaddin
Copy link
Contributor Author

ziyaddin commented Feb 5, 2020

@mikehardy yes, it works for me so far. I have also done patch-package procedure as you said in our previous discussion.

Copy link
Member

@Ehesp Ehesp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mikehardy
Copy link
Collaborator

Cool - thanks guys. The v5.x.x branch is still CI challenged (and it's not really worth it to fix) but I am able to run all the tests locally and manage a release.

I'd like to have a few more things batched (if possible) prior to a release so I'll merge this but not release it just now.

Since you've got patch-package going that shouldn't have a real impact for you, you'll get a nice patch-package warning in the future when it does come out and the patch doesn't apply, so no monitoring needed really

Cheers

@mikehardy mikehardy merged commit 401eecc into invertase:v5.x.x Feb 5, 2020
@ziyaddin
Copy link
Contributor Author

ziyaddin commented Feb 5, 2020

@mikehardy thanks! While editing, I came across with more cases of data: Object inside index.d.ts. Should we fix them?

@mikehardy
Copy link
Collaborator

I dunno - I'm open to PRs like that I'm just not sure if they are worth the effort with v5.x.x in maintenance mode. That's totally up to you. I'd mostly just check vs the v6 branch and if they are already fixed there maybe let them rest as the future has fixes and the current is maybe not worth the effort

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
plugin: messaging FCM only - ( messaging() ) - do not use for Notifications tools: typings TypeScript / Flow Workflow: Waiting for User Response Blocked waiting for user response.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants