In D19740#244818, @joshuaspence wrote:I think maybe we should keep it as an empty n_CLASS_ATTRIBUTES in case attributes are added later.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed Advanced Search
Advanced Search
Advanced Search
Oct 10 2018
Oct 10 2018
wjiang added a revision to T4334: Support PHP5.4+ syntax in XHPAST: D19741: Let lint rules support anonymous classes.
Oct 9 2018
Oct 9 2018
wjiang added a revision to T4334: Support PHP5.4+ syntax in XHPAST: D19740: Fix class attribute node in anonymous class.
Oct 8 2018
Oct 8 2018
wjiang added a revision to T4334: Support PHP5.4+ syntax in XHPAST: D19736: Add support for anonymous class.
Sep 18 2017
Sep 18 2017
Aug 6 2017
Aug 6 2017
wjiang retitled D18351: Let `ArcanistNamespaceFirstStatementXHPASTLinterRule` support `declare` statements from Let `ArcanistNamespaceFirstStatementXHPASTLinterRule` support `declare` statemnts to Let `ArcanistNamespaceFirstStatementXHPASTLinterRule` support `declare` statements.
wjiang added a comment to D18351: Let `ArcanistNamespaceFirstStatementXHPASTLinterRule` support `declare` statements.
Maybe the name of ArcanistNamespaceFirstStatementXHPASTLinterRule is not quite proper now ? Perhaps ArcanistNamespaceStatementPositionXHPASTLinterRule could be replacement.
May 16 2017
May 16 2017
wjiang added a comment to T12716: PHPCompatibility lint rule can't handle namespaced class/function name..
In T12716#223717, @chad wrote:I assume this is T4334
wjiang updated the task description for T12716: PHPCompatibility lint rule can't handle namespaced class/function name..
May 4 2017
May 4 2017
wjiang updated the diff for D17825: Let default parameters linter rule support `...` in variadic function.
Minor
wjiang updated subscribers of D17825: Let default parameters linter rule support `...` in variadic function.
- Minor
- Add applyStandard
Apr 24 2017
Apr 24 2017
Add final
Apr 20 2017
Apr 20 2017
In T12601#220840, @epriestley wrote:The only behavior of --lintall is to make warnings act like errors. Just raise everything at error severity to achieve the same thing without patching anything.
In T12601#220824, @epriestley wrote:You are probably raising messages at "warning" severity, but want to raise them at "error" severity. See, e.g., here for a description:
Dec 11 2016
Dec 11 2016
Is this diff still in progress ?
Dec 1 2016
Dec 1 2016
- fix tests
- Add more tests and fix regex