rspec/rules/S5850/php/rule.adoc

== Why is this an issue?

include::../description.adoc[]


=== Noncompliant code example

[source,php]
----
/^a|b|c$/
----


=== Compliant solution

[source,php]
----
/^(?:a|b|c)$/
----

or


[source,php]
----
/^a$|^b$|^c$/
----

or, if you do want the anchors to only apply to ``++a++`` and ``++c++`` respectively:


[source,php]
----
/(?:^a)|b|(?:c$)/
----
migrate rule descriptions to new education format 2023-05-03 11:06:20 +02:00			`== Why is this an issue?`

Modify rule S5850: Add PHP as covered language (#334) 2021-09-13 16:20:17 +02:00			`include::../description.adoc[]`


migrate rule descriptions to new education format 2023-05-03 11:06:20 +02:00			`=== Noncompliant code example`
Modify rule S5850: Add PHP as covered language (#334) 2021-09-13 16:20:17 +02:00
RULEAPI-661: Add syntax coloring 2022-02-04 17:28:24 +01:00			`[source,php]`
Modify rule S5850: Add PHP as covered language (#334) 2021-09-13 16:20:17 +02:00			`----`
			`/^a\|b\|c$/`
			`----`


migrate rule descriptions to new education format 2023-05-03 11:06:20 +02:00			`=== Compliant solution`
Modify rule S5850: Add PHP as covered language (#334) 2021-09-13 16:20:17 +02:00
RULEAPI-661: Add syntax coloring 2022-02-04 17:28:24 +01:00			`[source,php]`
Modify rule S5850: Add PHP as covered language (#334) 2021-09-13 16:20:17 +02:00			`----`
			`/^(?:a\|b\|c)$/`
			`----`

			`or`


RULEAPI-661: Add syntax coloring 2022-02-04 17:28:24 +01:00			`[source,php]`
Modify rule S5850: Add PHP as covered language (#334) 2021-09-13 16:20:17 +02:00			`----`
			`/^a$\|^b$\|^c$/`
			`----`

			or, if you do want the anchors to only apply to ``++a++`` and ``++c++`` respectively:


RULEAPI-661: Add syntax coloring 2022-02-04 17:28:24 +01:00			`[source,php]`
Modify rule S5850: Add PHP as covered language (#334) 2021-09-13 16:20:17 +02:00			`----`
			`/(?:^a)\|b\|(?:c$)/`
			`----`