BBCodeModuleInterface::__construct()
last analyzed

Size

Total Lines 1

Duplication

Lines 0
Ratio 0 %

Importance

Changes 0
Metric Value
dl 0
loc 1
c 0
b 0
f 0
1
<?php
2
/**
3
 * Interface BBCodeModuleInterface
4
 *
5
 * @filesource   BBCodeModuleInterface.php
6
 * @created      24.04.2018
7
 * @package      chillerlan\BBCode\Output
8
 * @author       smiley <[email protected]>
9
 * @copyright    2018 smiley
10
 * @license      MIT
11
 */
12
13
namespace chillerlan\BBCode\Output;
14
15
use chillerlan\Settings\SettingsContainerInterface;
16
use Psr\Log\LoggerInterface;
17
use Psr\SimpleCache\CacheInterface;
18
19
interface BBCodeModuleInterface{
20
21
	/**
22
	 * BBCodeModuleInterface constructor.
23
	 *
24
	 * @param \chillerlan\Settings\SettingsContainerInterface $options
25
	 * @param \Psr\SimpleCache\CacheInterface       $cache
26
	 * @param \Psr\Log\LoggerInterface              $logger
27
	 */
28
	public function __construct(SettingsContainerInterface $options, CacheInterface $cache, LoggerInterface $logger);
0 ignored issues
show
Documentation introduced by
For interfaces and abstract methods it is generally a good practice to add a @return annotation even if it is just @return void or @return null, so that implementors know what to do in the overridden method.

For interface and abstract methods, it is impossible to infer the return type from the immediate code. In these cases, it is generally advisible to explicitly annotate these methods with a @return doc comment to communicate to implementors of these methods what they are expected to return.

Loading history...
29
30
	/**
31
	 * @return array
32
	 */
33
	public function getTags():array;
34
35
	/**
36
	 * @return array
37
	 */
38
	public function getSingleTags():array;
39
40
	/**
41
	 * @return array
42
	 */
43
	public function getNoparse():array;
44
45
}
46