Conversation
|
By analyzing the blame information on this pull request, we identified @philikon, @nicklockwood and @vjeux to be potential reviewers. |
|
cc @dmmiller who's running the effort of unifying iOS and Android apis :) |
|
Could the diff be expressed as a rename of |
|
I think we should show a warning when someone tries to use the events on Android. Also, deep linking on Android is not supported on master, I've a pull request open here #4320 . However, I need to test it with my latest changes before I get it merged. |
|
BTW, currently we have 3 different files, LinkingIOS, IntentAndroid and Linking. We could merge them to a single Linking.js file and just export it as LinkingIOS, IntentAndroid and Linking for backward compatibility. |
|
Is "Linking" a good name for this? I can't say I'm a fan of it. If we're renaming it anyway, might as well pick something we like. |
|
@nicklockwood Any ideas for a Good name? |
|
Something like Routing? or URLRouting? I don't know. Names are hard ¯_(ツ)_/¯ |
|
@nicklockwood Routing sounds like it has something to do with React (Native) Router :| Yeah, names are pretty damn hard :( |
|
Agree with you guys. How about @satya164: having one file and exporting it as linkingios, intentAndroid etc sounds like a good plan |
|
@chirag04 Nah, URL means, well URL (URL.openURL(url: string) is kinda weird), and History is more like what the Navigators does. |
|
yeah. let's wait for more suggestions. I will update the PR accordingly. My plan was to start a discussion around this with this PR :) |
|
Thanks for doing this! We should remove LinkingIOS and IntentAndroid in a followup PR, will need to update internal fb code with that. I don't mind the name Linking - it's used to open external "links". Looks like you need to rebase, sorry for the delay. Have many PRs in the queue and doing the branch cut for 0.17. |
|
Adding a label so I don't forget about this PR. |
|
@mkonicek I'm on vacation till 26th Dec. I will try to rebase and submit the follow up PR soon. Keeping it open till then. |
|
No problem, enjoy your vacation @chirag04 :) |
|
@chirag04 updated the pull request. |
There was a problem hiding this comment.
property Linking Property not found in Object.create
There was a problem hiding this comment.
Is the bot linting against my PR branch or master?
|
@chirag04 updated the pull request. |
|
@mkonicek This should be go to go now. let me know we need any modification. Happy to submit subsequent PR to remove other files once we get this merged. |
There was a problem hiding this comment.
property Linking Property not found in Object.create
|
@chirag04 updated the pull request. |
|
@chirag04 |
|
How about the name
|
|
@bozzmob Not a fan of it. There are method like |
|
@satya164 Agree with you. |
|
Looks like it's a constant on iOS and a method on Android? Don't have a strong preference - if it's hard to make it a constant on Android can we just make it a function with a callback in |
|
Couldn't you implement popInitialURL on Android by calling getInitialURL internally and then popping to it? |
|
@nicklockwood We could. But it can change, and having it in a constant will be confusing. |
|
Yeah, I'm not sure when to call |
|
closing in favor of #5336. Let's continue the discussion there. |
A lot of code is redundant in IntentAndroid and LinkingIOS. This bridges that gap.
Not sure what we should do with IntentAndroid.js and LinkingIOS.js if we merge this.
cc @mkonicek @ide @brentvatne