Proposal:
Vue\Codebase::scan only parses .vue files (plus standalone .ts for TYPE declarations). A codebase whose client is plain TypeScript modules — exported functions, consts, classes — cannot be judged at all by a frontend detector. I wanted a naming rule (identifiers that read as English clauses) to apply to resources/js the same way it applies to src, and there is no selector that reaches a function or const declared in a .ts module. Hand-rolling a regex over the source is exactly what the writing-detectors skill forbids, so the rule simply cannot be written today.
Filed via commandments feature-request from a consumer project.
Proposal:
Vue\Codebase::scan only parses .vue files (plus standalone .ts for TYPE declarations). A codebase whose client is plain TypeScript modules — exported functions, consts, classes — cannot be judged at all by a frontend detector. I wanted a naming rule (identifiers that read as English clauses) to apply to resources/js the same way it applies to src, and there is no selector that reaches a function or const declared in a .ts module. Hand-rolling a regex over the source is exactly what the writing-detectors skill forbids, so the rule simply cannot be written today.
Filed via
commandments feature-requestfrom a consumer project.