-
-
Notifications
You must be signed in to change notification settings - Fork 142
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
v2.12.0 (issue210-address-as-parameter) - Adding ADDRESS as a potential parameter #272
Conversation
I just noticed you have another PR that is going to convert this library into TypeScript (v3.0.0). If you want to do that first then we can go in and make similar changes we can do that too. |
Hi @trevorrd - apologies for the delay! The Typescript migration has now been completed, so if you're willing to update this, I'm happy to get this merged. Apologies for the duplicated work! |
…to this fork. Exported a MapException class, and made more changes to the maps to include passing an address as a query string to those individual maps. Still have a number to update until it's fully done.
…ll address to each of the map apps. A few either did NOT support passing the destination address or it wasn't documented. Ready to open a PR.
…eed to double check the compare files then a PR may be ready.
Hey Thomas (@tschoffelen), Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is amazing work! One quick suggestion on the README, but looking very much forward to merging this soon!
Thanks again!!
It's taken me way too long (apologies again), but it's merged! Thanks again @trevorrd for the amazing work on this, quite a big new feature you've shipped here! |
🎉 This PR is included in version 3.4.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Update: After some debugging it looks like the url structure is wrong. Referring to the google docs here: https://developers.google.com/maps/documentation/urls/get-started it says all urls should have However for the address line it instead uses whereas the docs about says it should be PR to fix is here: #294 Would be great to get this merged asap if possible as we caught this issue during testing for a big app update which meant to be going out today :D |
Nice catch! Yes, open a bug ticket. I'm not sure how I missed that small query string parameter. I know I used it in my project for work and must have missed it as I was adding it to this library. If we could get the ticket opened and change that, it would be great. Thanks! |
There's already a PR up for it here: #294 |
This PR is to address issue210-address-as-parameter. I've made the changes to now allow developers to use an address instead of latitude and longitude coordinates. This is what I had commented on earlier and you, Thomas Schoffelen, had commented and said,
It's not a use case I personally have, because I want to send users to a specific location rather than doing a search, but I can understand why that would be useful. I'm still happy to accept a PR for that functionality if you'd like to add it!
So here is my pull request. Please review it, give me any feedback, if you see anything I need to update or change please let me know.