Skip to content
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

vars-on-top documentation is lying #1234

Closed
lo1tuma opened this issue Sep 9, 2014 · 2 comments · Fixed by #1237
Closed

vars-on-top documentation is lying #1234

lo1tuma opened this issue Sep 9, 2014 · 2 comments · Fixed by #1237
Labels
archived due to age This issue has been archived; please open a new issue for any further discussion bug ESLint is working incorrectly documentation Relates to ESLint's documentation

Comments

@lo1tuma
Copy link
Member

lo1tuma commented Sep 9, 2014

The documentation of the vars-on-top rule says that it only requires var-statements to be on the top of functions but it also warns if a var-statement is not on the top of the global scope.

michaelficarra added a commit to michaelficarra/eslint that referenced this issue Sep 9, 2014
@nzakas nzakas added documentation Relates to ESLint's documentation bug ESLint is working incorrectly labels Sep 9, 2014
@nzakas
Copy link
Member

nzakas commented Sep 9, 2014

Yeah, that was just changed.

nzakas added a commit that referenced this issue Sep 9, 2014
Docs: fix up vars-on-top documentation (fixes #1234)
@nzakas nzakas reopened this Sep 9, 2014
@nzakas
Copy link
Member

nzakas commented Sep 9, 2014

The title of the page and the short description on the rules index is still incorrect.

lo1tuma added a commit to lo1tuma/eslint that referenced this issue Sep 10, 2014
@nzakas nzakas closed this as completed in 3d0c9b7 Sep 10, 2014
nzakas added a commit that referenced this issue Sep 10, 2014
Docs: fix vars-on-top documentation (fixes #1234).
fczuardi added a commit to fczuardi/eslint that referenced this issue Mar 7, 2015
fczuardi added a commit to fczuardi/eslint that referenced this issue Mar 8, 2015
# The first commit's message is:

Fix: remove typo that caused a crash (fixes eslint#1234)

# This is the 2nd commit message:

choose ecmaVersion 6 when ecmaFeatures.modules is true
TheIronDev added a commit to TheIronDev/eslint that referenced this issue May 14, 2016
Simple fix to one of the new issues. If a node is falsy, then it
definitely will NOT contain an assignment.

Updating commit msg to include eslint#6161

Maybe this will work?
* (fixes eslint#1234)
ljharb added a commit to ljharb/eslint that referenced this issue Aug 4, 2016
edmorley added a commit to edmorley/eslint that referenced this issue Apr 27, 2017
Previously the array could have contained more elements than expected.
@eslint-deprecated eslint-deprecated bot locked and limited conversation to collaborators Feb 7, 2018
@eslint-deprecated eslint-deprecated bot added the archived due to age This issue has been archived; please open a new issue for any further discussion label Feb 7, 2018
Sawtaytoes added a commit to Sawtaytoes/eslint that referenced this issue Feb 28, 2020
…t#1234)

This adds the `ConditionalExpression` option to the `indent` rule which allows controlling the indent value of `?` and `:` where they were previously hardcoded to `1`.

Default behavior is unchanged.
Sawtaytoes added a commit to Sawtaytoes/eslint that referenced this issue Mar 2, 2020
…t#1234)

This adds the `ConditionalExpression` option to the `indent` rule which allows controlling the indent value of `?` and `:` where they were previously hardcoded to `1`.

Default behavior is unchanged.
Sawtaytoes added a commit to Sawtaytoes/eslint that referenced this issue Mar 3, 2020
…t#1234)

This adds the `ConditionalExpression` option to the `indent` rule which allows controlling the indent value of `?` and `:` where they were previously hardcoded to `1`.

Default behavior is unchanged.
Sawtaytoes added a commit to Sawtaytoes/eslint that referenced this issue Mar 5, 2020
…t#1234)

This adds the `ConditionalExpression` option to the `indent` rule which allows controlling the indent value of `?` and `:` where they were previously hardcoded to `1`.

Default behavior is unchanged.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
archived due to age This issue has been archived; please open a new issue for any further discussion bug ESLint is working incorrectly documentation Relates to ESLint's documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants