bigcommerce-api-php Update Resource.php

$fields should be public so you can access its individual members directly

Apr 18 '15 02:04 sudosoul

Coverage remained the same at 61.4% when pulling 0aa766b0959ae3988b24149fc6273294c3e34cc7 on mullinsr:patch-2 into 15aaf1bbbc7a02fb6dbb3c59457039be33446858 on bigcommerce:master.

Apr 18 '15 02:04 coveralls

Coverage decreased (-2.9%) to 58.5% when pulling 43fb56681934925e03cfbd5ce2df03f1e7092a59 on mullinsr:patch-2 into 15aaf1bbbc7a02fb6dbb3c59457039be33446858 on bigcommerce:master.

Apr 18 '15 02:04 coveralls

Coverage decreased (-2.9%) to 58.5% when pulling 43fb56681934925e03cfbd5ce2df03f1e7092a59 on mullinsr:patch-2 into 15aaf1bbbc7a02fb6dbb3c59457039be33446858 on bigcommerce:master.

Apr 18 '15 02:04 coveralls

Coverage decreased (-2.9%) to 58.5% when pulling 43fb56681934925e03cfbd5ce2df03f1e7092a59 on mullinsr:patch-2 into 15aaf1bbbc7a02fb6dbb3c59457039be33446858 on bigcommerce:master.

Apr 18 '15 02:04 coveralls

Coverage decreased (-2.9%) to 58.5% when pulling 43fb56681934925e03cfbd5ce2df03f1e7092a59 on mullinsr:patch-2 into 15aaf1bbbc7a02fb6dbb3c59457039be33446858 on bigcommerce:master.

Apr 18 '15 02:04 coveralls

I added oAuth support on Client and Connection, so far it seems to be very stable with this new updated library (connection would intermittently drop on old oauth branch). oAuth is configured by calling:

$array = array(
  'store_hash' => 'xxx',
  'client_id'     => 'xxx',
  'oauth_token' => 'xx'
);
Bigcommerce::configure($array,true);

My intentions for this pr was to bring up the protected fields issue. Feel free to modify oauth changes as needed.

Apr 18 '15 02:04 sudosoul