These are very common in READMEs and makes it easier to have projects that are mirrored between github and phorge
Details
- Reviewers
- None
- Group Reviewers
O1: Blessed Committers
Running it on our local phabricator/phorge instance
Diff Detail
- Repository
- rP Phorge
- Branch
- more-gfmy
- Lint
Lint Errors Severity Location Code Message Error src/infrastructure/markup/blockrule/PhutilRemarkupCodeBlockRule.php:51 XHP5 Use of Undeclared Variable - Unit
Tests Skipped - Build Status
Buildable 63 Build 63: arc lint + arc unit
Event Timeline
src/infrastructure/markup/blockrule/PhutilRemarkupCodeBlockRule.php | ||
---|---|---|
77โ82 | Would it make sense to put the language parsing here instead of above? Essentially if we see a key here which doesn't exist in options, whose value is empty/null, and the key matches a known syntax language then we could specify the language here. | |
126โ129 | It may also make sense to update this area of the code. Possibly having the guesswork done here or at least updating the comment to clarify that this guessing should only occur if the user didn't specify lang or if we determined it was specified GFM style |
Sorry but this title seems somehow cryptic to me. Are we talking about this feature?
So it seems at the moment this syntax is supported:
```lang=php
Code
```
But not this syntax:
```php
Code
```
Isn't it?