Add formatting and automatic snippet-language detection for PHP in SQLBI Whiteboard.
Vote for this language
Add a 馃憤 reaction to this opening post to vote for formatting and automatic detection for PHP. We will use these votes to help prioritize languages. You can vote for more than one language. Please use reactions instead of adding a comment containing only '+1'.
If useful, leave a comment with a representative snippet and say whether formatting, automatic detection, or both matter most to you. Remove any confidential information before posting.
Scope
Highlighting and manual language selection are planned separately. This issue tracks the subsequent work to:
- Format the selected text container with F6, both in display mode and while editing.
- Recognize PHP on paste through Snippet format order, using conservative signals so notes and ambiguous snippets are not claimed incorrectly.
- Preserve program meaning and comments; leave invalid or unsupported snippets unchanged.
- Support snippets without requiring a project or separately installed developer tools, and keep formatting responsive.
- Add regression coverage for language-specific syntax and cross-language detection ambiguity.
Handle snippets with and without PHP opening tags and heredoc/nowdoc strings. Decide mixed PHP/HTML scope explicitly.
In-app voting link
The highlighting-only implementation will show a message when F6 is requested for PHP, with a link to this issue inviting a 馃憤 vote. It will leave the code unchanged and open GitHub only when the user chooses the link. This issue covers both requested capabilities; no delivery date is promised.
Add formatting and automatic snippet-language detection for PHP in SQLBI Whiteboard.
Vote for this language
Add a 馃憤 reaction to this opening post to vote for formatting and automatic detection for PHP. We will use these votes to help prioritize languages. You can vote for more than one language. Please use reactions instead of adding a comment containing only '+1'.
If useful, leave a comment with a representative snippet and say whether formatting, automatic detection, or both matter most to you. Remove any confidential information before posting.
Scope
Highlighting and manual language selection are planned separately. This issue tracks the subsequent work to:
Handle snippets with and without PHP opening tags and heredoc/nowdoc strings. Decide mixed PHP/HTML scope explicitly.
In-app voting link
The highlighting-only implementation will show a message when F6 is requested for PHP, with a link to this issue inviting a 馃憤 vote. It will leave the code unchanged and open GitHub only when the user chooses the link. This issue covers both requested capabilities; no delivery date is promised.