search

barryhennessy / google-api-php-client

Automatically exported from code.google.com/p/google-api-php-client
Apache License 2.0
0 stars 0 forks source link

Review and improve configuration of the libraries #287

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Several issues have arisen with regards to the current method of configuring 
the library, which requires the use of a global variable. This should be 
replaced with a cleaner method/methods. It may be worth considering file 
parsing, or an object based configuration.

Original issue reported on code.google.com by ianbar...@google.com on 22 Mar 2013 at 2:27

GoogleCodeExporter commented 8 years ago 
Issue 154 has been merged into this issue.

Original comment by ianbar...@google.com on 22 Mar 2013 at 2:27

GoogleCodeExporter commented 8 years ago 
Just bouncing this up priority for 0.7

Original comment by ianbar...@google.com on 28 Mar 2013 at 8:13

GoogleCodeExporter commented 8 years ago 
Note, we also need to look at removing some of the unnecessary content in there 
- specifically the legacy endpoint URLs. We might also want to consider 
injecting the auth/cache objects rather than specifying classnames, though 
mileage may vary there.

Original comment by ianbar...@google.com on 28 Mar 2013 at 8:17

GoogleCodeExporter commented 8 years ago 
This issue tracker is now closing. Development on the Google PHP client library 
moved to GitHub with the release of the 1.0.0-alpha, and now the 1.0 branch has 
reached beta status there will be no further releases of the 0.6 branch of the 
library. 

Please take a look at the latest version on 
https://github.com/google/google-api-php-client

For information on migrating, please take a look at this guide: 
https://developers.google.com/api-client-library/php/guide/migration

For general library support please ask a question on StackOverflow: 
http://stackoverflow.com/questions/tagged/google-api-php-client

If you are looking for support with a specific API, please contact the team 
working with that API via StackOverflow or their preferred support mechanism. 

If your issue still exists with the new version of the library, please raise a 
bug in the GitHub issue tracker with a minimal code sample. 

Thanks!

Original comment by ianbar...@google.com on 22 Jan 2014 at 4:53