OAuthDataStore::new_access_token()   A
last analyzed

Complexity

Conditions 1
Paths 1

Size

Total Lines 1
Code Lines 0

Duplication

Lines 0
Ratio 0 %

Importance

Changes 0
Metric Value
cc 1
eloc 0
nc 1
nop 3
dl 0
loc 1
rs 10
c 0
b 0
f 0
1
<?php
2
3
class OAuthDataStore {
4
  function lookup_consumer($consumer_key) {
0 ignored issues
show
Best Practice introduced by
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
5
    // implement me
6
  }
7
8
  function lookup_token($consumer, $token_type, $token) {
0 ignored issues
show
Best Practice introduced by
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
9
    // implement me
10
  }
11
12
  function lookup_nonce($consumer, $token, $nonce, $timestamp) {
0 ignored issues
show
Best Practice introduced by
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
13
    // implement me
14
  }
15
16
  function new_request_token($consumer, $callback = null) {
0 ignored issues
show
Best Practice introduced by
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
17
    // return a new token attached to this consumer
18
  }
19
20
  function new_access_token($token, $consumer, $verifier = null) {
0 ignored issues
show
Best Practice introduced by
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
21
    // return a new access token attached to this consumer
22
    // for the user associated with this token if the request token
23
    // is authorized
24
    // should also invalidate the request token
25
  }
26
27
}
28