Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: add a clear note that we do not strictly follow PSR/PER #2394

Merged
merged 2 commits into from
Aug 6, 2024
Merged

docs: add a clear note that we do not strictly follow PSR/PER #2394

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1897718
docs: add a clear note that we do not strictly follow PSR/PER
Kenneth-Sills Aug 6, 2024
fdf3095
docs: improve verbiage of standard adherence note
Kenneth-Sills Aug 6, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,6 +37,10 @@ Prettier is an opinionated code formatter. It enforces a consistent style by par

This plugin adds support for the PHP language to Prettier.

> [!NOTE]
>
> This plugin has always used PSR / PER as guidance when making formatting decisions, but has never aimed to be fully PSR / PER compliant. The idea behind this plugin is to stay reasonably close to how Prettier for JS works.

### Can this be used in production?

We're considering the plugin to be stable when pure PHP files are formatted. Formatting of files that contain mixed PHP and HTML is still considered unstable - please see [open issues with the tag "inline"](https://github.com/prettier/plugin-php/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3Ainline) for details.
Expand Down
Loading