FM / doc

/var/www/vhosts/ihelp.ro/httpdocs/vendor/slevomat/coding-standard/doc/

/var/www/vhosts/ihelp.ro/httpdocs/vendor/slevomat/coding-standard/doc

Name	Size	Mode	Actions
arrays.md	1616	0644	edit dl rm
attributes.md	1799	0644	edit dl rm
classes.md	12804	0644	edit dl rm
commenting.md	5860	0644	edit dl rm
complexity.md	289	0644	edit dl rm
control-structures.md	9492	0644	edit dl rm
exceptions.md	1171	0644	edit dl rm
files.md	2619	0644	edit dl rm
functions.md	4904	0644	edit dl rm
namespaces.md	7673	0644	edit dl rm
numbers.md	625	0644	edit dl rm
operators.md	1137	0644	edit dl rm
php.md	3169	0644	edit dl rm
strings.md	392	0644	edit dl rm
type-hints.md	9653	0644	edit dl rm
variables.md	752	0644	edit dl rm
whitespaces.md	623	0644	edit dl rm

Edit: /var/www/vhosts/ihelp.ro/httpdocs/vendor/slevomat/coding-standard/doc/attributes.md (1799B)

## Attributes

#### SlevomatCodingStandard.Attributes.AttributeAndTargetSpacing 🔧

Sniff checks lines count between attribute and its target (or target's documentation comment).

Sniff provides the following settings:

* `allowOnSameLine`: allow attribute and its target to be placed on the same line (default value is false)
* `linesCount`: lines count between attribute and its target

#### SlevomatCodingStandard.Attributes.AttributesOrder 🔧

Requires order of attributes. When more attributes are in one `#[]`, e.g. `#[One, Two]`, the first attribute name is used to resolve the order.

Sniff provides the following settings:

* `order`: required order of attributes. Supports prefixes, eg. `ORM\`, and mask , eg. `AppAssert*`.
* `orderAlphabetically`: order attributes alphabetically. Boolean value, default `false`.

Only one order can be set.

```xml
<rule ref="SlevomatCodingStandard.Attributes.AttributesOrder">
	<properties>
		<property name="order" type="array">
			<element value="ORM\Table"/>
			<element value="ORM\"/>
			<element value="One"/>
			<element value="Two"/>
		</property>
	</properties>
</rule>
```

#### SlevomatCodingStandard.Attributes.DisallowAttributesJoining 🔧

Requires that only one attribute can be placed inside `#[]` (no comma-separated list). In case of more attributes applied, they are split into individual `#[]` blocks.

#### SlevomatCodingStandard.Attributes.DisallowMultipleAttributesPerLine 🔧

Disallows multiple attributes of some target on same line.
This sniff treats multiple attributes declared inside one `#[]` as a single attribute. See `DisallowAttributesJoining` to modify this behavior.

#### SlevomatCodingStandard.Attributes.RequireAttributeAfterDocComment 🔧

Requires that attributes are always after documentation comment.

## Attributes #### SlevomatCodingStandard.Attributes.AttributeAndTargetSpacing 🔧 Sniff checks lines count between attribute and its target (or target's documentation comment). Sniff provides the following settings: * `allowOnSameLine`: allow attribute and its target to be placed on the same line (default value is false) * `linesCount`: lines count between attribute and its target #### SlevomatCodingStandard.Attributes.AttributesOrder 🔧 Requires order of attributes. When more attributes are in one `#[]`, e.g. `#[One, Two]`, the first attribute name is used to resolve the order. Sniff provides the following settings: * `order`: required order of attributes. Supports prefixes, eg. `ORM\`, and mask , eg. `AppAssert*`. * `orderAlphabetically`: order attributes alphabetically. Boolean value, default `false`. Only one order can be set. ```xml ``` #### SlevomatCodingStandard.Attributes.DisallowAttributesJoining 🔧 Requires that only one attribute can be placed inside `#[]` (no comma-separated list). In case of more attributes applied, they are split into individual `#[]` blocks. #### SlevomatCodingStandard.Attributes.DisallowMultipleAttributesPerLine 🔧 Disallows multiple attributes of some target on same line. This sniff treats multiple attributes declared inside one `#[]` as a single attribute. See `DisallowAttributesJoining` to modify this behavior. #### SlevomatCodingStandard.Attributes.RequireAttributeAfterDocComment 🔧 Requires that attributes are always after documentation comment.