-
Notifications
You must be signed in to change notification settings - Fork 580
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
YAMLLintBear does not like .travis.yml due to missing start/end #923
Comments
refeed
added a commit
to refeed/coala-bears
that referenced
this issue
Oct 31, 2016
Disable YAMLLint rule `document-start` by default because many YAML files have no need for start and end markers, but user still can enable it by using `document_start=true` setting. Add unit tests for YAMLLintBear. Closes coala#923
refeed
added a commit
to refeed/coala-bears
that referenced
this issue
Nov 5, 2016
Disable YAMLLint rule `document-start` by default because many YAML files have no need for start and end markers, but user still can enable it by using `document_start=true` setting. Closes coala#923
refeed
added a commit
to refeed/coala-bears
that referenced
this issue
Nov 5, 2016
Disable YAMLLint rule `document-start` by default because many YAML files have no need for start and end markers, but user still can enable it by using `document_start=true` setting. Closes coala#923
refeed
added a commit
to refeed/coala-bears
that referenced
this issue
Nov 5, 2016
Disable YAMLLint rule `document-start` by default because many YAML files have no need for start and end markers, but user still can enable it by using `document_start=true` setting. Closes coala#923
adrienverge
added a commit
to adrienverge/coala-bears
that referenced
this issue
Feb 8, 2017
Some projects use documents starts (`---`) in YAML documents (for example Ansible, OpenStack, yamllint), others don't. Since these markers are required when declaring multiple documents in a single .yaml file (see the spec [1]), it is a bad idea to forbid them. This commit disables the `document-start` rule by default, instead of forcing / forbidding the use of these markers. [1]: http://yaml.org/spec/1.2/spec.html#id2800132 Closes: coala#1417 Fixes: coala#923 coala#965
adrienverge
added a commit
to adrienverge/coala-bears
that referenced
this issue
Feb 8, 2017
Some projects use documents starts (`---`) in YAML documents (for example Ansible, OpenStack, yamllint), others don't. Since these markers are required when declaring multiple documents in a single .yaml file (see the spec [1]), it is a bad idea to forbid them. This commit disables the `document-start` rule by default, instead of forcing / forbidding the use of these markers. [1]: http://yaml.org/spec/1.2/spec.html#id2800132 Closes: coala#1417 Fixes: coala#923 coala#965
adrienverge
added a commit
to adrienverge/coala-bears
that referenced
this issue
Feb 8, 2017
Some projects use documents starts (`---`) in YAML documents (for example Ansible, OpenStack, yamllint), others don't. Since these markers are required when declaring multiple documents in a single .yaml file (see the spec [1]), it is a bad idea to forbid them. This commit disables the `document-start` rule by default, instead of forcing / forbidding the use of these markers. [1]: http://yaml.org/spec/1.2/spec.html#id2800132 Closes coala#1417 Fixes coala#923 coala#965
adrienverge
added a commit
to adrienverge/coala-bears
that referenced
this issue
Feb 8, 2017
Some projects use documents starts (`---`) in YAML documents (for example Ansible, OpenStack, yamllint), others don't. Since these markers are required when declaring multiple documents in a single .yaml file (see the spec [1]), it is a bad idea to forbid them. This commit disables the `document-start` rule by default, instead of forcing / forbidding the use of these markers. [1]: http://yaml.org/spec/1.2/spec.html#id2800132 Closes coala#1417 Related to coala#923 and coala#965
gosom
pushed a commit
to gosom/coala-bears
that referenced
this issue
Jul 15, 2017
Disable YAMLLint rule `document-start` by default because many YAML files have no need for start and end markers, but user still can enable it by using `document_start=true` setting. Closes coala#923
gosom
pushed a commit
to gosom/coala-bears
that referenced
this issue
Jul 15, 2017
Some projects use documents starts (`---`) in YAML documents (for example Ansible, OpenStack, yamllint), others don't. Since these markers are required when declaring multiple documents in a single .yaml file (see the spec [1]), it is a bad idea to forbid them. This commit disables the `document-start` rule by default, instead of forcing / forbidding the use of these markers. [1]: http://yaml.org/spec/1.2/spec.html#id2800132 Closes coala#1417 Related to coala#923 and coala#965
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Many yaml files have no need for start and end markers. It should be an option to disable
document-start
and IMO it should be disabled by defaultThe text was updated successfully, but these errors were encountered: