GitHub Access Token became invalid

It seems like the GitHub access token used for retrieving details about this repository from GitHub became invalid. This might prevent certain types of inspections from being run (in particular, everything related to pull requests).
Please ask an admin of your repository to re-new the access token on this website.
Completed
Push — develop ( 586ade...5bf1ed )
by Stuart
23:53
created

HTTP::fromHttp()   A

Complexity

Conditions 1
Paths 1

Size

Total Lines 4
Code Lines 2

Duplication

Lines 0
Ratio 0 %

Importance

Changes 1
Bugs 0 Features 0
Metric Value
c 1
b 0
f 0
dl 0
loc 4
rs 10
cc 1
eloc 2
nc 1
nop 0
1
<?php
2
3
/**
4
 * Copyright (c) 2011-present Mediasift Ltd
5
 * All rights reserved.
6
 *
7
 * Redistribution and use in source and binary forms, with or without
8
 * modification, are permitted provided that the following conditions
9
 * are met:
10
 *
11
 *   * Redistributions of source code must retain the above copyright
12
 *     notice, this list of conditions and the following disclaimer.
13
 *
14
 *   * Redistributions in binary form must reproduce the above copyright
15
 *     notice, this list of conditions and the following disclaimer in
16
 *     the documentation and/or other materials provided with the
17
 *     distribution.
18
 *
19
 *   * Neither the names of the copyright holders nor the names of his
20
 *     contributors may be used to endorse or promote products derived
21
 *     from this software without specific prior written permission.
22
 *
23
 * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
24
 * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
25
 * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
26
 * FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
27
 * COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
28
 * INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
29
 * BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
30
 * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
31
 * CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
32
 * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
33
 * ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
34
 * POSSIBILITY OF SUCH DAMAGE.
35
 *
36
 * @category  Libraries
37
 * @package   Storyplayer/Modules/HTTP
38
 * @author    Stuart Herbert <[email protected]>
39
 * @copyright 2011-present Mediasift Ltd www.datasift.com
40
 * @license   http://www.opensource.org/licenses/bsd-license.php  BSD License
41
 * @link      http://datasift.github.io/storyplayer
42
 */
43
44
namespace Storyplayer\SPv2\Modules;
45
46
use DataSift\Stone\HttpLib\HttpClientResponse;
47
use DataSift\Storyplayer\PlayerLib\StoryTeller;
48
49
use Storyplayer\SPv2\Modules\HTTP\ExpectsHttpResponse;
50
use Storyplayer\SPv2\Modules\HTTP\FromHttp;
51
use Storyplayer\SPv2\Modules\HTTP\UsingHttp;
52
53
class HTTP
54
{
55
    /**
56
     * returns the ExpectsHttpResponse module
57
     *
58
     * This module provides a great way to test that you got the response that
59
     * you expected from your usingHttp() / fromHttp() call.
60
     *
61
     * If the response doesn't meet your expectations, an exception will be
62
     * thrown.
63
     *
64
     * @param  HttpClientResponse $httpResponse
65
     *         the return value from usingHttp()->post() et al
66
     * @return ExpectsHttpResponse
67
     */
68
    public static function expectsHttpResponse(HttpClientResponse $httpResponse)
69
    {
70
        return new ExpectsHttpResponse(StoryTeller::instance(), [$httpResponse]);
71
    }
72
73
    /**
74
     * returns the FromHttp module
75
     *
76
     * This module provides support for making GET requests over HTTP.
77
     *
78
     * SSL/TLS is fully supported.
79
     *
80
     * If you are using self-signed certificates, you will need to set
81
     * 'moduleSettings.http.validateSsl = false' in your test environment's
82
     * config file first.
83
     *
84
     * To make PUT, POST and DELETE requests, use the UsingHttp module.
85
     *
86
     * @return FromHttp
87
     */
88
    public static function fromHttp()
89
    {
90
        return new FromHttp(StoryTeller::instance());
91
    }
92
93
    /**
94
     * returns the UsingHttp module
95
     *
96
     * This module provides support for making PUT, POST and DELETE requests
97
     * over HTTP (basically, any HTTP verb that should change state at the other
98
     * end).
99
     *
100
     * SSL/TLS is fully supported.
101
     *
102
     * If you are using self-signed certificates, you will need to set
103
     * 'moduleSettings.http.validateSsl = false' in your test environment's
104
     * config file first.
105
     *
106
     * To make GET requests, use the FromHttp module.
107
     *
108
     * @return UsingHttp
109
     */
110
    function usingHttp()
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...
111
    {
112
        return new UsingHttp(StoryTeller::instance());
113
    }
114
115
}
116