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

Response handling for native communicator #1360

Merged
merged 2 commits into from
Jul 31, 2024
Merged

Conversation

vishnumad
Copy link
Contributor

Summary

  • Makes Communicator a singleton per keys url
  • Add handleResponseUrl function that routes the response to the communicator
  • Remove expo-linking

How did you test your changes?

@cb-heimdall
Copy link
Collaborator

cb-heimdall commented Jul 30, 2024

✅ Heimdall Review Status

Requirement Status More Info
Reviews 1/1
Denominator calculation
Show calculation
1 if user is bot 0
1 if user is external 0
From .codeflow.yml 1
Additional review requirements
Show calculation
Max 0
0
From CODEOWNERS 0
Global minimum 0
Max 1
1
1 if commit is unverified 0
Sum 1

@@ -36,7 +36,6 @@
"peerDependencies": {
"@react-native-async-storage/async-storage": "*",
"expo": "*",
"expo-linking": "*",
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Removing expo-linking -- We don't need to depend on this. Users might get their deeplinks from other places like Branch

@vishnumad vishnumad marked this pull request as ready for review July 31, 2024 22:40
@vishnumad vishnumad merged commit 715502f into master Jul 31, 2024
8 of 9 checks passed
@vishnumad vishnumad deleted the vishnu/handle-response branch July 31, 2024 22:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants