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

Review the feedback by ncruces and create the appropriate issues #236

Closed
thinkingserious opened this issue Jun 15, 2016 · 1 comment
Closed
Labels
status: help wanted requesting help from the community type: community enhancement feature request not on Twilio's roadmap

Comments

@thinkingserious
Copy link
Contributor

@ncruces I closed the other issue since the bug is fixed. I'll be reviewing your feedback to create specific issues. Feel free to do so before I get to it. Thanks!

#234 (comment)

@thinkingserious thinkingserious added type: community enhancement feature request not on Twilio's roadmap status: help wanted requesting help from the community labels Jun 15, 2016
@thinkingserious
Copy link
Contributor Author

@ncruces @critot

Following is an update based on @ncruces' feedback (thanks again!):

With regards to the dynamic URL builder, you can skip that process by passing in your path. We will update the documentation to reflect this. Also, we plan to allow you to pass in your own HTTP client, in that case, you can choose to a client that does not use dynamic URL building.

Naming Conventions: #239

Regarding “stuff not amenable to async/await”, I believe that relates to: #235

Object/Collection initializers: #240

Please let me know if I missed anything or if the tickets need updates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: help wanted requesting help from the community type: community enhancement feature request not on Twilio's roadmap
Projects
None yet
Development

No branches or pull requests

1 participant