should PEAR.Functions.FunctionCallSignature.Indent be applied on javascript files ?

[naveen17797]

Bug Description

should PEAR.Functions.FunctionCallSignature.Indent be applied on javascript files ?

This is related to issue #2395, i tried to fix the file with @wordpress/scripts format command, yet it didn't fix this file. So is it right to ignore javascript files from this sniff ?

[jrfnl]

@naveen17797 Javascript support is being removed from PHPCS and by extension from WPCS. Use Javascript specific tooling like eslint/jslint and such instead.

[naveen17797]

@jrfnl So if i understood correctly, its safe to disable wpcs for all other file extensions except php ? I am using wpcs version 3.0.1

[jrfnl]

@naveen17797 Providing you use tooling like eslint/jslint etc, then, yes, I'd recommend disabling JS scanning via WPCS.

[naveen17797]

Thanks for the clarification :-)

…

On Wed, 3 Apr, 2024, 3:59 pm Juliette, ***@***.***> wrote: @naveen17797 <https://github.com/naveen17797> Providing you use tooling like eslint/jslint etc, then, yes, I'd recommend disabling JS scanning via WPCS. — Reply to this email directly, view it on GitHub <#2441 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEKFGSTS4HRAKBDCGVNTAELY3PK2DAVCNFSM6AAAAABFU57AJ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZUGE4TAMBUGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>