View GitHub Repository JATE

Schedule Inspection
Subscribe

Parser::parseFileMan()   A
last analyzed

↳ Parent: Project

Complexity

Conditions 4
Paths 4

Size

Total Lines 13

Duplication

Lines 0
Ratio 0 %

Importance

Changes 0
Metric Value
cc 4
nc 4
nop 3
dl 0
loc 13
rs 9.8333
c 0
b 0
f 0
1 
<?php
0 ignored issues
– show
Coding Style Compatibility introduced by
For compatibility and reusability of your code, PSR1 recommends that a file should introduce either new symbols (like classes, functions, etc.) or have side-effects (like outputting something, or including other files), but not both at the same time. The first symbol is defined on line 4 and the first side effect is on line 2.

The PSR-1: Basic Coding Standard recommends that a file should either introduce new symbols, that is classes, functions, constants or similar, or have side effects. Side effects are anything that executes logic, like for example printing output, changing ini settings or writing to a file.

The idea behind this recommendation is that merely auto-loading a class should not change the state of an application. It also promotes a cleaner style of programming and makes your code less prone to errors, because the logic is not spread out all over the place.

To learn more about the PSR-1, please see the PHP-FIG site on the PSR-1.

Loading history...
2 
  requireComponents("Adapters");
3 
  jRequire("../JException/JException.php");
4 
  class Parser {
0 ignored issues
– show
Coding Style Compatibility introduced by
PSR1 recommends that each class must be in a namespace of at least one level to avoid collisions.

You can fix this by adding a namespace to your class:

namespace YourVendor;

class YourClass { }

When choosing a vendor namespace, try to pick something that is not too generic to avoid conflicts with other libraries.

Loading history...
5 
    private static function setParser ( $_type ) {
6 
      $parser = null;
0 ignored issues
– show
Unused Code introduced by
$parser is not used, you could remove the assignment.

This check looks for variable assignements that are either overwritten by other assignments or where the variable is not used subsequently.

$myVar = 'Value';
$higher = false;

if (rand(1, 6) > 3) {
    $higher = true;
} else {
    $higher = false;
}

Both the $myVar assignment in line 1 and the $higher assignment in line 2 are dead. The first because $myVar is never used and the second because $higher is always overwritten for every possible time line.

Loading history...
7 
      $_type = strtolower($_type);
8 
      switch ($_type) {
9 
        case "twig":
10 
        case "sql":
11 
          $parser = new TwigAdapter();
12 
        break;
13 
        case "jate":
14 
          $parser = new JTagAdapter();
15 
        break;
16 
        case 'jade':
17 
        case "pug":
18 
          $parser = new PugAdapter();
19 
        break;
20 
        case "md":
21 
        case "markdown":
22 
        case "parsedown":
23 
          $parser = new ParsedownAdapter();
24 
        break;
25 
        default:
26 
          $parser = -1;
27 
        break;
28 
      }
29 
      return $parser;
30 
    }
31 
    public static function parseText( $_text, $_parameters = [], $_type = "html" ) {
32 
      if(!is_string($_text) || !is_string($_type))
33 
        throw new JException("Parameter must be a string.");
34 
      if(!is_array($_parameters))
35 
        throw new JException("Parameter must be an array.");
36 
      $parser = self::setParser($_type);
37 
      if($parser === -1)
38 
        return $_text;
39 
      return $parser->drawText($_text, $_parameters);
40 
    }
41 
    public static function parseFileMan( $_path, $_parameters = [], $_type = "html"  ) {
42 
      if(!is_string($_path))
43 
        throw new JException("Parameter must be a string.");
44 
      if(!file_exists($_path))
45 
        throw new JException("File [$_path] not found.");
46 
      $string = file_get_contents($_path);
47 
      try {
48 
        $text = self::parseText($string, $_parameters, $_type);
49 
      } catch (Exception $e) {
50 
        throw new JException($e->getMessage());
51 
      }
52 
      return $text;
53 
    }
54 
    public static function parseFile( $_path, $_parameters = [] ) {
55 
      if(!is_string($_path))
56 
        throw new JException("Parameter must be a string.");
57 
      $extension = explode(".", $_path);
58 
      $extension = $extension[count($extension)-1];
59 
      $extension = strtolower($extension);
60 
      try {
61 
        $text = self::parseFileMan($_path, $_parameters, $extension);
62 
      } catch (Exception $e) {
63 
        throw new JException($e->getMessage());
64 
      }
65 
      return $text;
66 
    }
67 
  }
68 
?>
0 ignored issues
– show
Best Practice introduced by
It is not recommended to use PHP's closing tag ?> in files other than templates.

Using a closing tag in PHP files that only contain PHP code is not recommended as you might accidentally add whitespace after the closing tag which would then be output by PHP. This can cause severe problems, for example headers cannot be sent anymore.

A simple precaution is to leave off the closing tag as it is not required, and it also has no negative effects whatsoever.

Loading history...
69