定制 mavsolutions/yaml-linter 二次开发

按需修改功能、优化性能、对接业务系统,提供一站式技术支持

邮箱:yvsm@zunyunkeji.com | QQ:316430983 | 微信:yvsm316

mavsolutions/yaml-linter

最新稳定版本:1.0.0

Composer 安装命令:

composer require mavsolutions/yaml-linter

包简介

A Symfony cli command utility for checking YAML file syntax

README 文档

README

Wrapper for symfony/yaml's LintCommand (see Symfony/Yaml)

Call it like Symfony's LintCommand with filename as arguments, single files as exclude-Option and with additional option excludePattern.
ExcludePattern are parsed with symfony/finder (see Symfony/Finder) as path and all matching yaml|yml are added to LintCommand's exclude-options.

use-case

In some projects one might use local composer-packages which have their own frontend-buildchain. This buildchain might integrate some third-party libraries into your project-structure with malformed yaml-files which you don't need to care for.

├── composer.json
├── src
…
└── packages
    └── local-subpackage
        ├── composer.json
        ├── Configuration
        ├── Documentation
        ├── Resources
        │   ├── node_modules
        │   │   ├── some third party npm-packages
        │   │   └── …
        │   ├── package.json
        │   ├── Sources
        │   ├── webpack.config.js
        │   └── yarn.lock
        …

When scanning this whole project with a yaml-lint-command I got some errors from node_modules-subdirectories. You should for sure validate those error-messages, create several pull-requests to the third-party repos, patch your local files while waiting for pr to be merged - but to be honest in real life you only need a "green pipeline".

Example

vandor/bin/yaml-linter src --excludePattern=thirdParty

统计信息

  • 总下载量: 73
  • 月度下载量: 0
  • 日度下载量: 0
  • 收藏数: 0
  • 点击次数: 0
  • 依赖项目数: 0
  • 推荐数: 0

GitHub 信息

  • Stars: 0
  • Watchers: 1
  • Forks: 0
  • 开发语言: PHP

其他信息

  • 授权协议: GPL-2.0-or-later
  • 更新时间: 2023-03-23