Closed (fixed)
Project:
Twilio SMS Integration
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
22 Nov 2016 at 17:53 UTC
Updated:
9 Feb 2017 at 20:42 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
dpiPR originally at: https://github.com/dpi/sms_twilio/pull/2
Comment #3
bradjones1From a quick glance it looks like sms_twilio doesn't have a dependency on SMS Framework... Is the idea that is going to happen, or would we need to refactor the incoming logic in that PR to integrate in with this module as it stands? I believe there's been a conversation about that, but I'm late to the party?
Comment #4
dpiIf SMS Framework is not installed then what is going to call the incoming logic? I would guess no-one.
As the code is, there does not have to be a dependency. Since this project is dedicated to SMS Framework then it would make sense. Its ultimately @chrisrockwell choice.
As an aside: I find it easier to develop modules if I do not have to uninstall dependent modules. For example, if a site builder hoses his install of SMS Framework, then he does not have to uninstall sms_twilio. Dependent modules primary configuration can stay intact. (gateway instances will of course be removed by the Configuration API)
Only discussion about that is what we discussed in https://github.com/dpi/sms_twilio/pull/2#issue-183274703
Comment #5
chrisrockwell commented@bradjones1 I don't have the intention of making this stand-alone. I need to catch up on the discussion on github but it's safe to assume the integration will remain.
Comment #6
chrisrockwell commentedAdded related issue #2832601: Incoming message handling tweaks
Comment #7
chrisrockwell commentedComment #8
dpiComment #9
dpiComment #10
bradjones1I have updated the PR on Github to incorporate the new API.
https://github.com/dpi/sms_twilio/pull/2#issuecomment-276535498
Comment #11
chrisrockwell commentedI'm uploading my untested work-in-progress, which is an attempt at combining @bradjones1' work and mine (I apologize for not getting it out sooner). @dpi made some comments on the PR linked in #10 that need to be addressed, namely:
I did not have media handling and I prefer the way @bradjones1 separated out
buildIncomingFromRequestas I had it all inprocessIncoming.The way I'm handling validation might need to be discussed. I *think* we should be explicitly using the generated route for the signature.
Thanks all!
Comment #12
chrisrockwell commentedShould be TwilioValidation.php
Comment #13
dpi@ #12
generally most @file blocks are no longer required per coding standards. In this case, the file block should be moved to describe the class:
Comment #14
bradjones1Sorry for all the minor commits on the Github PR, but I did get a chance to test this locally against Twilio and it looks like our work merged together, well. Attached is a patch version of the PR at this moment.
Comment #15
dpi+30 KB?
There should be interdiffs if sticking to patchflow:
Comment #16
chrisrockwell commentedSomething got messed up with the patch @bradjones1. For example, none of these should be in Twilio.php (
incomingis deprecated,validateis renamed and in a Utility class. I'll take a look at the PR's on GitHub.Comment #17
chrisrockwell commentedI merged in the changes in @bradjones1 fork and am uploading it here.
I'm seeing the benefit of doing the grunt of the work on github and then merging it here as needed so I'll work on transitioning to that.
Comment #18
chrisrockwell commentedComment #19
chrisrockwell commentedComment #20
chrisrockwell commentedFixes/adds error handling. With this I've confirmed incoming using a live Twilio account.
Comment #21
chrisrockwell commentedSomewhere the dependency on SMS Framework was removed.
@dpi in #4:
Is this why it's a suggestion instead of a requirement? Without SMS Framework this isn't usable, no?
Comment #22
chrisrockwell commentedI merged @bradjones1 PR here: http://cgit.drupalcode.org/sms_twilio/commit/?id=9a085f9 so that we could keep the history.
Comment #23
chrisrockwell commented