Completed
Pull Request — master (#6)
by AJ
12:51
created

ShopifyAPIComponent::startup()   A

Complexity

Conditions 1
Paths 1

Size

Total Lines 4
Code Lines 2

Duplication

Lines 0
Ratio 0 %

Code Coverage

Tests 0
CRAP Score 2

Importance

Changes 0
Metric Value
dl 0
loc 4
ccs 0
cts 2
cp 0
rs 10
c 0
b 0
f 0
cc 1
eloc 2
nc 1
nop 1
crap 2
1
<?php
2
/**
3
 * CakePHPify : CakePHP Plugin for Shopify API Authentication
4
 * Copyright (c) Multidimension.al (http://multidimension.al)
5
 * Github : https://github.com/multidimension-al/cakephpify
6
 *
7
 * Licensed under The MIT License
8
 * For full copyright and license information, please see the LICENSE file
9
 * Redistributions of files must retain the above copyright notice.
10
 *
11
 * @copyright     (c) Multidimension.al (http://multidimension.al)
12
 * @link          https://github.com/multidimension-al/cakephpify CakePHPify Github
13
 * @license       http://www.opensource.org/licenses/mit-license.php MIT License
14
 */
15
16
namespace Multidimensional\Shopify\Controller\Component;
17
18
use Cake\Core\Configure;
19
use Cake\Controller\Component;
20
use Cake\Routing\Router;
21
use Cake\Network\Http\Client;
22
use Cake\Event\Event;
23
use Cake\Network\Exception\NotImplementedException;
24
25
class ShopifyAPIComponent extends Component
0 ignored issues
show
Coding Style introduced by
The property $api_key is not named in camelCase.

This check marks property names that have not been written in camelCase.

In camelCase names are written without any punctuation, the start of each new word being marked by a capital letter. Thus the name database connection string becomes databaseConnectionString.

Loading history...
Coding Style introduced by
The property $shop_domain is not named in camelCase.

This check marks property names that have not been written in camelCase.

In camelCase names are written without any punctuation, the start of each new word being marked by a capital letter. Thus the name database connection string becomes databaseConnectionString.

Loading history...
Coding Style introduced by
The property $shared_secret is not named in camelCase.

This check marks property names that have not been written in camelCase.

In camelCase names are written without any punctuation, the start of each new word being marked by a capital letter. Thus the name database connection string becomes databaseConnectionString.

Loading history...
Coding Style introduced by
The property $is_private_app is not named in camelCase.

This check marks property names that have not been written in camelCase.

In camelCase names are written without any punctuation, the start of each new word being marked by a capital letter. Thus the name database connection string becomes databaseConnectionString.

Loading history...
Coding Style introduced by
The property $private_app_password is not named in camelCase.

This check marks property names that have not been written in camelCase.

In camelCase names are written without any punctuation, the start of each new word being marked by a capital letter. Thus the name database connection string becomes databaseConnectionString.

Loading history...
26
{
27
  
28
    public $api_key;
0 ignored issues
show
Coding Style introduced by
$api_key does not seem to conform to the naming convention (^[a-z][a-zA-Z0-9]*$).

This check examines a number of code elements and verifies that they conform to the given naming conventions.

You can set conventions for local variables, abstract classes, utility classes, constant, properties, methods, parameters, interfaces, classes, exceptions and special methods.

Loading history...
29
30
    private $shop_domain;
0 ignored issues
show
Coding Style introduced by
$shop_domain does not seem to conform to the naming convention (^[a-z][a-zA-Z0-9]*$).

This check examines a number of code elements and verifies that they conform to the given naming conventions.

You can set conventions for local variables, abstract classes, utility classes, constant, properties, methods, parameters, interfaces, classes, exceptions and special methods.

Loading history...
31
    private $token;
32
    private $shared_secret;
0 ignored issues
show
Coding Style introduced by
$shared_secret does not seem to conform to the naming convention (^[a-z][a-zA-Z0-9]*$).

This check examines a number of code elements and verifies that they conform to the given naming conventions.

You can set conventions for local variables, abstract classes, utility classes, constant, properties, methods, parameters, interfaces, classes, exceptions and special methods.

Loading history...
33
    private $is_private_app;
0 ignored issues
show
Coding Style introduced by
$is_private_app does not seem to conform to the naming convention (^[a-z][a-zA-Z0-9]*$).

This check examines a number of code elements and verifies that they conform to the given naming conventions.

You can set conventions for local variables, abstract classes, utility classes, constant, properties, methods, parameters, interfaces, classes, exceptions and special methods.

Loading history...
34
    private $private_app_password;
0 ignored issues
show
Coding Style introduced by
$private_app_password does not seem to conform to the naming convention (^[a-z][a-zA-Z0-9]*$).

This check examines a number of code elements and verifies that they conform to the given naming conventions.

You can set conventions for local variables, abstract classes, utility classes, constant, properties, methods, parameters, interfaces, classes, exceptions and special methods.

Loading history...
35
    private $nonce;
36
37
    public $controller = null;
38
39
    public function initialize(array $config = [])
40
    {
41
42
        parent::initialize($config);
43
        
44
      $this->api_key = isset($config['api_key']) ? $config['api_key'] : '';
45
				
46
      if (!empty($this->api_key)) {
47
48
        $this->shared_secret = Configure::read('Multidimensional/Shopify.' . $this->api_key . '.shared_secret');
49
        $this->scope = Configure::read('Multidimensional/Shopify.' . $this->api_key . '.scope');
0 ignored issues
show
Bug introduced by
The property scope does not exist. Did you maybe forget to declare it?

In PHP it is possible to write to properties without declaring them. For example, the following is perfectly valid PHP code:

class MyClass { }

$x = new MyClass();
$x->foo = true;

Generally, it is a good practice to explictly declare properties to avoid accidental typos and provide IDE auto-completion:

class MyClass {
    public $foo;
}

$x = new MyClass();
$x->foo = true;
Loading history...
50
        $this->is_private_app = Configure::read('Multidimensional/Shopify.' . $this->api_key . '.is_private_app');
51
        $this->private_app_password = Configure::read('Multidimensional/Shopify.' . $this->api_key . '.private_app_password');        
52
53
      } else {
54
55
        throw new NotImplementedException(__('Shopify API key not found'));
56
57
      }
58
59
      if (!$this->shared_secret) {
60
61
        throw new NotImplementedException(__('Shopify shared secret not found'));
62
63
      }
64
      
65
    }
66
67
    public function startup(Event $event)
68
    {
69
        $this->setController($event->subject());
70
    }
71
72
    public function setController($controller)
73
    {
74
        $this->controller = $controller;
75
        if (!isset($this->controller->paginate)) {
76
            $this->controller->paginate = [];
77
        }
78
79
    }
80
81
    public function setShopDomain($shopDomain)
0 ignored issues
show
Documentation introduced by
The return type could not be reliably inferred; please add a @return annotation.

Our type inference engine in quite powerful, but sometimes the code does not provide enough clues to go by. In these cases we request you to add a @return annotation as described here.

Loading history...
82
    {
83
        return $this->shop_domain = $shopDomain;
84
    }
85
86
    public function getShopDomain()
0 ignored issues
show
Documentation introduced by
The return type could not be reliably inferred; please add a @return annotation.

Our type inference engine in quite powerful, but sometimes the code does not provide enough clues to go by. In these cases we request you to add a @return annotation as described here.

Loading history...
87
    {
88
        return $this->shop_domain;
89
    }
90
91
    public function setAccessToken($token)
0 ignored issues
show
Documentation introduced by
The return type could not be reliably inferred; please add a @return annotation.

Our type inference engine in quite powerful, but sometimes the code does not provide enough clues to go by. In these cases we request you to add a @return annotation as described here.

Loading history...
92
    {
93
        return $this->token = $token;
94
    }
95
96
    public function callsMade()
97
    {
98
        return $this->shopApiCallLimitParam(0);
99
    }
100
101
    public function callLimit()
102
    {
103
        return $this->shopApiCallLimitParam(1);
104
    }
105
106
    public function callsLeft($responseHeaders)
0 ignored issues
show
Unused Code introduced by
The parameter $responseHeaders is not used and could be removed.

This check looks from parameters that have been defined for a function or method, but which are not used in the method body.

Loading history...
107
    {
108
        return $this->callLimit() - $this->callsMade();
109
    }
110
111
    /**
112
     * @param string $method
113
     * @param string $path
114
     */
115
    public function call($method, $path, $params = [])
0 ignored issues
show
Documentation introduced by
The return type could not be reliably inferred; please add a @return annotation.

Our type inference engine in quite powerful, but sometimes the code does not provide enough clues to go by. In these cases we request you to add a @return annotation as described here.

Loading history...
116
    {
117
118
        if (!$this->_isReady()) {
119
            return false;
120
        }
121
122
        if (!in_array($method, ['POST', 'PUT', 'GET', 'DELETE'])) {
123
            return false;
124
        }
125
126
        $http = new Client([
127
            'host' => $this->shop_domain,
128
            'scheme' => 'https',
129
            'headers' => (($this->is_private_app != 'true') ? (['X-Shopify-Access-Token' => $this->token]) : []),
130
            'auth' => (($this->is_private_app != 'true') ? [] : (['username' => $this->api_key, 'password' => $this->private_app_password]))
131
        ]);
132
133
        $this->response = $http->{strtolower($method)}(
134
            $path,
135
            ((in_array($method, ['POST', 'PUT'])) ? json_encode($params) : $params),
136
            ((in_array($method, ['POST', 'PUT'])) ? ['type' => 'json'] : [])
137
        );
138
        $this->response = $this->response->json;
139
140
        return (is_array($this->response) && (count($this->response) > 0)) ? array_shift($this->response) : $this->response;
141
    }
142
143
    /**
144
     * @param int $index
145
     */
146
    private function shopApiCallLimitParam($index)
147
    {
148
        $params = explode("/", $this->response->getHeaderLine('http_x_shopify_shop_api_call_limit'));
0 ignored issues
show
Bug introduced by
The method getHeaderLine() does not exist on Cake\Network\Response. Did you maybe mean header()?

This check marks calls to methods that do not seem to exist on an object.

This is most likely the result of a method being renamed without all references to it being renamed likewise.

Loading history...
149
150
        return (int)$params[$index];
151
    }
152
153
    public function getAuthorizeUrl($shopDomain, $redirectUrl)
154
    {
155
156
        $url = 'https://' . $shopDomain . '/admin/oauth/authorize?client_id=' . $this->api_key;
157
        $url .= '&scope=' . urlencode($this->scope);
158
        $url .= '&redirect_uri=' . urlencode($redirectUrl);
159
        $url .= '&state=' . $this->getNonce($shopDomain);
0 ignored issues
show
Unused Code introduced by
The call to ShopifyAPIComponent::getNonce() has too many arguments starting with $shopDomain.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
160
161
        return $url;
162
    }
163
164
    public function getAccessToken($shopDomain, $code)
0 ignored issues
show
Documentation introduced by
The return type could not be reliably inferred; please add a @return annotation.

Our type inference engine in quite powerful, but sometimes the code does not provide enough clues to go by. In these cases we request you to add a @return annotation as described here.

Loading history...
165
    {
166
167
        $this->shop_domain = $shopDomain;
168
169
        $http = new Client([
170
            'host' => $shopDomain,
171
            'scheme' => 'https'
172
        ]);
173
174
        $response = $http->post('/admin/oauth/access_token', 'client_id=' . $this->api_key .
175
                                    '&client_secret=' . $this->shared_secret .
176
                                    '&code=' . $code);
177
        $response = $response->json;
178
        ;
179
180
        if (isset($response['access_token'])) {
181
            $this->token = $response['access_token'];
182
183
            return $this->token;
184
        } else {
185
            return false;
186
        }
187
    }
188
189
    public function setNonce($shopDomain)
190
    {
191
192
        return $this->nonce = md5(strtolower($shopDomain));
193
    }
194
195
196
    public function getNonce()
197
    {
198
199
        return $this->nonce;
200
    }
201
202
    public function validDomain($shopDomain)
0 ignored issues
show
Coding Style introduced by
function validDomain() does not seem to conform to the naming convention (^(?:is|has|should|may|supports)).

This check examines a number of code elements and verifies that they conform to the given naming conventions.

You can set conventions for local variables, abstract classes, utility classes, constant, properties, methods, parameters, interfaces, classes, exceptions and special methods.

Loading history...
Unused Code introduced by
The parameter $shopDomain is not used and could be removed.

This check looks from parameters that have been defined for a function or method, but which are not used in the method body.

Loading history...
203
    {
204
205
        return true;
206
    }
207
208
    public function getShopData()
0 ignored issues
show
Documentation introduced by
The return type could not be reliably inferred; please add a @return annotation.

Our type inference engine in quite powerful, but sometimes the code does not provide enough clues to go by. In these cases we request you to add a @return annotation as described here.

Loading history...
209
    {
210
211
        return $this->call('GET', '/admin/shop.json');
212
    }
213
214
    public function validateHMAC($query)
0 ignored issues
show
Coding Style introduced by
function validateHMAC() does not seem to conform to the naming convention (^(?:is|has|should|may|supports)).

This check examines a number of code elements and verifies that they conform to the given naming conventions.

You can set conventions for local variables, abstract classes, utility classes, constant, properties, methods, parameters, interfaces, classes, exceptions and special methods.

Loading history...
215
    {
216
217
        if (!is_array($query) || empty($query['hmac']) || !is_string($query['hmac']) || (isset($query['state']) && $query['state'] != $this->getNonce($query['shop']))) {
0 ignored issues
show
Unused Code introduced by
The call to ShopifyAPIComponent::getNonce() has too many arguments starting with $query['shop'].

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
218
            return false;
219
        }
220
221
        $dataString = [];
222
223
        foreach ($query as $key => $value) {
224
            $key = $this->_urlEncode(str_replace('=', '%3D', $key));
225
            $value = $this->_urlEncode($value);
226
            if ($key != 'hmac') {
227
                $dataString[] = $key . '=' . $value;
228
            }
229
        }
230
231
        sort($dataString);
232
        $string = implode("&", $dataString);
233
234
        return $query['hmac'] == hash_hmac('sha256', $string, $this->shared_secret);
235
    }
236
237
    /**
238
     * @param string $url
239
     */
240
    private function _urlEncode($url)
241
    {
242
243
        $url = str_replace('&', '%26', $url);
244
        $url = str_replace('%', '%25', $url);
245
246
        return $url;
247
    }
248
249
    private function _isReady()
0 ignored issues
show
Coding Style introduced by
function _isReady() does not seem to conform to the naming convention (^(?:is|has|should|may|supports)).

This check examines a number of code elements and verifies that they conform to the given naming conventions.

You can set conventions for local variables, abstract classes, utility classes, constant, properties, methods, parameters, interfaces, classes, exceptions and special methods.

Loading history...
250
    {
251
        return strlen($this->shop_domain) > 0 && strlen($this->token) > 0;
252
    }
253
}
254