XMLParse   A
last analyzed

Complexity

Total Complexity 3

Size/Duplication

Total Lines 44
Duplicated Lines 0 %

Coupling/Cohesion

Components 0
Dependencies 1

Importance

Changes 0
Metric Value
wmc 3
c 0
b 0
f 0
lcom 0
cbo 1
dl 0
loc 44
rs 10

2 Methods

Rating   Name   Duplication   Size   Complexity  
A extract() 0 13 2
A generate() 0 11 1
1
<?php
2
namespace Wechat\Utils\Code;
3
4
use Wechat\Utils\Code\ErrorCode;
5
6
/**
7
 * XMLParse class
8
 *
9
 * 提供提取消息格式中的密文及生成回复消息格式的接口.
10
 */
11
class XMLParse
12
{
13
14
    /**
15
     * 提取出xml数据包中的加密消息
16
     *
17
     * @param string $xmltext 待提取的xml字符串
18
     *
19
     * @return string 提取出的加密消息字符串
20
     */
21
    public function extract($xmltext)
22
    {
23
        try {
24
            $object     = simplexml_load_string($xmltext, 'SimpleXMLElement', LIBXML_NOCDATA);
25
            $encrypt    = $object->Encrypt;
0 ignored issues
show
Bug introduced by
The property Encrypt does not seem to exist in SimpleXMLElement.

An attempt at access to an undefined property has been detected. This may either be a typographical error or the property has been renamed but there are still references to its old name.

If you really want to allow access to undefined properties, you can define magic methods to allow access. See the php core documentation on Overloading.

Loading history...
26
            $tousername = $object->ToUserName;
0 ignored issues
show
Bug introduced by
The property ToUserName does not seem to exist in SimpleXMLElement.

An attempt at access to an undefined property has been detected. This may either be a typographical error or the property has been renamed but there are still references to its old name.

If you really want to allow access to undefined properties, you can define magic methods to allow access. See the php core documentation on Overloading.

Loading history...
27
28
            return [0, $encrypt, $tousername];
29
        } catch (Exception $e) {
0 ignored issues
show
Bug introduced by
The class Wechat\Utils\Code\Exception does not exist. Did you forget a USE statement, or did you not list all dependencies?

Scrutinizer analyzes your composer.json/composer.lock file if available to determine the classes, and functions that are defined by your dependencies.

It seems like the listed class was neither found in your dependencies, nor was it found in the analyzed files in your repository. If you are using some other form of dependency management, you might want to disable this analysis.

Loading history...
30
            //print $e . "\n";
0 ignored issues
show
Unused Code Comprehensibility introduced by
50% of this comment could be valid code. Did you maybe forget this after debugging?

Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.

The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.

This check looks for comments that seem to be mostly valid code and reports them.

Loading history...
31
            return [ErrorCode::$ParseXmlError, null, null];
32
        }
33
    }
34
35
    /**
36
     * 生成xml消息
37
     *
38
     * @param string $encrypt   加密后的消息密文
39
     * @param string $signature 安全签名
40
     * @param string $timestamp 时间戳
41
     * @param string $nonce     随机字符串
42
     */
43
    public function generate($encrypt, $signature, $timestamp, $nonce)
44
    {
45
        $format = "<xml>
46
<Encrypt><![CDATA[%s]]></Encrypt>
47
<MsgSignature><![CDATA[%s]]></MsgSignature>
48
<TimeStamp>%s</TimeStamp>
49
<Nonce><![CDATA[%s]]></Nonce>
50
</xml>";
51
52
        return sprintf($format, $encrypt, $signature, $timestamp, $nonce);
53
    }
54
}
55