Refactor NULL and TRUE/FALSE to use their lowercase variant #5064
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Within the documentation there are many inconsistencies. One of those is how null and booleans are written.
At some places it is written as NULL where in other places null is used.
Within parameters you generally want to use the lowercase variants. And also when mentioning the type null on its own.
At places like var dump results, you generally want to use the uppercase variant to make it in line with what PHP returns.
This change tries to tackle these inconsistencies. I did my very best not to touch values that are irrelevant, for example the value NULL within SQL. But since it we touch a lot of different files, have a good look.
The same has been done with TRUE/FALSE. Though in those situations it is almost always the lowercase variant.