The property $_replacement is not named in camelCase.
This check marks property names that have not been written in camelCase.
In camelCase names are written without any punctuation, the start of each new word being marked
by a capital letter. Thus the name database connection string becomes databaseConnectionString.
The property $_spacing_regex is not named in camelCase.
This check marks property names that have not been written in camelCase.
In camelCase names are written without any punctuation, the start of each new word being marked
by a capital letter. Thus the name database connection string becomes databaseConnectionString.
It is generally recommended to explicitly declare the visibility for methods.
Adding explicit visibility (private, protected, or public) is generally
recommend to communicate to other developers how, and from where this method
is intended to be used.
It is recommend to declare an explicit visibility for setReplacementValue.
Generally, we recommend to declare visibility for all methods in your source code.
This has the advantage of clearly communication to other developers, and also
yourself, how this method should be consumed.
If you are not sure which visibility to choose, it is a good idea to start with
the most restrictive visibility, and then raise visibility as needed, i.e.
start with private, and only raise it to protected if a sub-class needs
to have access, or public if an external class needs access.
The method _filter_attributes is not named in camelCase.
This check marks method names that have not been written in camelCase.
In camelCase names are written without any punctuation, the start of each new word being marked
by a capital letter. Thus the name database connection string becomes databaseConnectionString.
This check marks property names that have not been written in camelCase.
In camelCase names are written without any punctuation, the start of each new word being marked by a capital letter. Thus the name database connection string becomes
databaseConnectionString
.