pds/composer-script-names
Composer 安装命令:
composer require pds/composer-script-names
包简介
Standard for Composer script names.
README 文档
README
This publication describes a standard suitable for all PHP packages regarding Composer script names.
Please see https://github.com/php-pds/composer-script-names_research for background information.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this publication are to be interpreted as described in RFC 2119.
Summary
Script names in the composer.json file MUST be lower-case, and MUST use dashes
as word separators.
The composer.json file MUST use these script names for these purposes:
If the composer.json file defines a script to ... |
... then it MUST be named: |
|---|---|
| Run tests using a default configuration | test |
| Run tests using a default configuration, with coverage generation | test-coverage |
| Run tests using alternative configurations or approaches | test-* (see below) |
| Run a coding style fixer and/or code linter using a default configuration | cs-fix |
| Run static analysis using a default configuration | analyse OR analyze |
| Run multiple QA scripts or commands in sequence | check |
Naming Convention
Script names in the composer.json file MUST be lower-case, and MUST use dashes
as word separators.
Examples of compliant script names:
foofoo-barfoo-bar-baz
Examples of non-compliant script names:
Foofoo:barfoo_bar:Baz
Script Names
test
If the composer.json file defines a script to run tests using a default
configuration, it MUST be named test.
This publication does not otherwise define the test tooling.
test-coverage
If the composer.json file defines a script to run tests using a default
configuration, with coverage generation, it MUST be named test-coverage.
This publication does not otherwise define the test coverage tooling.
test-*
If the composer.json file defines a script to run tests using alternative
configurations or approaches, it MUST use the prefix test- with a descriptive
suffix.
Examples:
test-behaviortest-filtertest-integationtest-system
Aside from test-coverage, this publication does not otherwise define the
meaning of any test-* descriptive suffix.
cs-fix
If the composer.json file defines a script to run a coding style fixer
and/or code linter using a default configuration, it MUST be named cs-fix.
This publication does not otherwise define the style fixer or code linter tooling.
analyse or analyze
If the composer.json file defines a script to run static analysis using a
default configuration, it MUST be named EITHER analyse OR analyze.
N.b.: The naming alternatives reflect differences in typical usage by American and British English speakers.
This publication does not otherwise define the static analysis tooling.
check
If the composer.json file defines a script to run multiple quality-assurance
scripts or commands in sequence, it MUST be named check.
This publication does not otherwise define the specific scripts or commands, nor the order in which they are to run.
pds/composer-script-names 适用场景与选型建议
pds/composer-script-names 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 6.15k 次下载、GitHub Stars 达 31, 最近一次更新时间为 2023 年 04 月 06 日, 在 PHP 生态内属于活跃度较高的组件。
我们在过去多个企业项目中使用过 pds/composer-script-names 或与其功能相近的方案,如果你在选型或落地过程中遇到问题,例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查,欢迎联系我们协助评估。
基于 pds/composer-script-names 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。
线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。
承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。
统计信息
- 总下载量: 6.15k
- 月度下载量: 0
- 日度下载量: 0
- 收藏数: 31
- 点击次数: 9
- 依赖项目数: 35
- 推荐数: 0
其他信息
- 授权协议: CC-BY-SA-4.0
- 更新时间: 2023-04-06