cltk/annotations

View on GitHub

Showing 18 of 18 total issues

Similar blocks of code found in 2 locations. Consider refactoring.
Open

export const findNoteEntities = (
  contentBlock: ContentBlock,
  callback: Function,
  contentState: ContentState
) => {
Severity: Major
Found in src/decorators/Annotation.js and 1 other location - About 3 hrs to fix
src/decorators/GreekProsody.js on lines 295..311

Duplicated Code

Duplicated code can lead to software that is hard to understand and difficult to change. The Don't Repeat Yourself (DRY) principle states:

Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.

When you violate DRY, bugs and maintenance problems are sure to follow. Duplicated code has a tendency to both continue to replicate and also to diverge (leaving bugs as two similar implementations differ in subtle ways).

Tuning

This issue has a mass of 98.

We set useful threshold defaults for the languages we support but you may want to adjust these settings based on your project guidelines.

The threshold configuration represents the minimum mass a code block must have to be analyzed for duplication. The lower the threshold, the more fine-grained the comparison.

If the engine is too easily reporting duplication, try raising the threshold. If you suspect that the engine isn't catching enough duplication, try lowering the threshold. The best setting tends to differ from language to language.

See codeclimate-duplication's documentation for more information about tuning the mass threshold in your .codeclimate.yml.

Refactorings

Further Reading

Similar blocks of code found in 2 locations. Consider refactoring.
Open

export const scansionStrategy = (
  contentBlock: ContentBlock,
  callback: Function,
  contentState: ContentState
) => {
Severity: Major
Found in src/decorators/GreekProsody.js and 1 other location - About 3 hrs to fix
src/decorators/Annotation.js on lines 10..26

Duplicated Code

Duplicated code can lead to software that is hard to understand and difficult to change. The Don't Repeat Yourself (DRY) principle states:

Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.

When you violate DRY, bugs and maintenance problems are sure to follow. Duplicated code has a tendency to both continue to replicate and also to diverge (leaving bugs as two similar implementations differ in subtle ways).

Tuning

This issue has a mass of 98.

We set useful threshold defaults for the languages we support but you may want to adjust these settings based on your project guidelines.

The threshold configuration represents the minimum mass a code block must have to be analyzed for duplication. The lower the threshold, the more fine-grained the comparison.

If the engine is too easily reporting duplication, try raising the threshold. If you suspect that the engine isn't catching enough duplication, try lowering the threshold. The best setting tends to differ from language to language.

See codeclimate-duplication's documentation for more information about tuning the mass threshold in your .codeclimate.yml.

Refactorings

Further Reading

File GreekProsody.js has 295 lines of code (exceeds 250 allowed). Consider refactoring.
Open

// @flow

import React from 'react'
import type { ContentBlock, ContentState } from 'draft-js'

Severity: Minor
Found in src/decorators/GreekProsody.js - About 3 hrs to fix

    Similar blocks of code found in 3 locations. Consider refactoring.
    Open

        if (diphthongs.includes(`${currentLetter}${sentence[index + 1]}`)) {
          const substr = sentence.substring(lastIndex, index + 2)
          const nextEl = [substr, lastIndex, index === 0 ? 2 : index + 2]
    
          lastIndex = index + 2
    Severity: Major
    Found in src/decorators/GreekProsody.js and 2 other locations - About 1 hr to fix
    src/decorators/GreekProsody.js on lines 140..147
    src/decorators/GreekProsody.js on lines 158..165

    Duplicated Code

    Duplicated code can lead to software that is hard to understand and difficult to change. The Don't Repeat Yourself (DRY) principle states:

    Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.

    When you violate DRY, bugs and maintenance problems are sure to follow. Duplicated code has a tendency to both continue to replicate and also to diverge (leaving bugs as two similar implementations differ in subtle ways).

    Tuning

    This issue has a mass of 68.

    We set useful threshold defaults for the languages we support but you may want to adjust these settings based on your project guidelines.

    The threshold configuration represents the minimum mass a code block must have to be analyzed for duplication. The lower the threshold, the more fine-grained the comparison.

    If the engine is too easily reporting duplication, try raising the threshold. If you suspect that the engine isn't catching enough duplication, try lowering the threshold. The best setting tends to differ from language to language.

    See codeclimate-duplication's documentation for more information about tuning the mass threshold in your .codeclimate.yml.

    Refactorings

    Further Reading

    Similar blocks of code found in 3 locations. Consider refactoring.
    Open

        if (vowels.includes(currentLetter)) {
          const substr = sentence.substring(lastIndex, index + 1)
          const nextEl = [substr, lastIndex, index === 0 ? 1 : index + 1]
    
          lastIndex = index + 1
    Severity: Major
    Found in src/decorators/GreekProsody.js and 2 other locations - About 1 hr to fix
    src/decorators/GreekProsody.js on lines 140..147
    src/decorators/GreekProsody.js on lines 149..156

    Duplicated Code

    Duplicated code can lead to software that is hard to understand and difficult to change. The Don't Repeat Yourself (DRY) principle states:

    Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.

    When you violate DRY, bugs and maintenance problems are sure to follow. Duplicated code has a tendency to both continue to replicate and also to diverge (leaving bugs as two similar implementations differ in subtle ways).

    Tuning

    This issue has a mass of 68.

    We set useful threshold defaults for the languages we support but you may want to adjust these settings based on your project guidelines.

    The threshold configuration represents the minimum mass a code block must have to be analyzed for duplication. The lower the threshold, the more fine-grained the comparison.

    If the engine is too easily reporting duplication, try raising the threshold. If you suspect that the engine isn't catching enough duplication, try lowering the threshold. The best setting tends to differ from language to language.

    See codeclimate-duplication's documentation for more information about tuning the mass threshold in your .codeclimate.yml.

    Refactorings

    Further Reading

    Similar blocks of code found in 3 locations. Consider refactoring.
    Open

        if (diaresis.includes(currentLetter)) {
          const substr = sentence.substring(lastIndex, index + 1)
          const nextEl = [substr, lastIndex, index === 0 ? 1 : index + 1]
    
          lastIndex = index + 1
    Severity: Major
    Found in src/decorators/GreekProsody.js and 2 other locations - About 1 hr to fix
    src/decorators/GreekProsody.js on lines 149..156
    src/decorators/GreekProsody.js on lines 158..165

    Duplicated Code

    Duplicated code can lead to software that is hard to understand and difficult to change. The Don't Repeat Yourself (DRY) principle states:

    Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.

    When you violate DRY, bugs and maintenance problems are sure to follow. Duplicated code has a tendency to both continue to replicate and also to diverge (leaving bugs as two similar implementations differ in subtle ways).

    Tuning

    This issue has a mass of 68.

    We set useful threshold defaults for the languages we support but you may want to adjust these settings based on your project guidelines.

    The threshold configuration represents the minimum mass a code block must have to be analyzed for duplication. The lower the threshold, the more fine-grained the comparison.

    If the engine is too easily reporting duplication, try raising the threshold. If you suspect that the engine isn't catching enough duplication, try lowering the threshold. The best setting tends to differ from language to language.

    See codeclimate-duplication's documentation for more information about tuning the mass threshold in your .codeclimate.yml.

    Refactorings

    Further Reading

    Function syllablize has 33 lines of code (exceeds 25 allowed). Consider refactoring.
    Open

    export const syllablize = (sentence: string): Array<[
      string,
      number,
      number
    ]> => {
    Severity: Minor
    Found in src/decorators/GreekProsody.js - About 1 hr to fix

      Function render has 33 lines of code (exceeds 25 allowed). Consider refactoring.
      Open

        render() {
          const {
            annotatableEditorState,
            noteEditorState,
            noteEditorReadOnly
      Severity: Minor
      Found in stories/Annotating/index.js - About 1 hr to fix

        Similar blocks of code found in 2 locations. Consider refactoring.
        Open

        export const argonautica = `εἰ δ᾽ ἄγε νῦν, Ἐρατώ, παρά θ᾽ ἵστασο, καί μοι ἔνισπε, 
        ἔνθεν ὅπως ἐς Ἰωλκὸν ἀνήγαγε κῶας Ἰήσων 
        Μηδείης ὑπ᾽ ἔρωτι. σὺ γὰρ καὶ Κύπριδος αἶσαν 
        ἔμμορες, ἀδμῆτας δὲ τεοῖς μελεδήμασι θέλγεις 
        παρθενικάς: τῶ καί τοι ἐπήρατον οὔνομ᾽ ἀνῆπται. 
        Severity: Major
        Found in stories/stubs.js and 1 other location - About 1 hr to fix
        stories/stubs.js on lines 3..46

        Duplicated Code

        Duplicated code can lead to software that is hard to understand and difficult to change. The Don't Repeat Yourself (DRY) principle states:

        Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.

        When you violate DRY, bugs and maintenance problems are sure to follow. Duplicated code has a tendency to both continue to replicate and also to diverge (leaving bugs as two similar implementations differ in subtle ways).

        Tuning

        This issue has a mass of 59.

        We set useful threshold defaults for the languages we support but you may want to adjust these settings based on your project guidelines.

        The threshold configuration represents the minimum mass a code block must have to be analyzed for duplication. The lower the threshold, the more fine-grained the comparison.

        If the engine is too easily reporting duplication, try raising the threshold. If you suspect that the engine isn't catching enough duplication, try lowering the threshold. The best setting tends to differ from language to language.

        See codeclimate-duplication's documentation for more information about tuning the mass threshold in your .codeclimate.yml.

        Refactorings

        Further Reading

        Similar blocks of code found in 2 locations. Consider refactoring.
        Open

        export const nicomachea = `[1447α] [8]
        περὶ ποιητικῆς αὐτῆς τε καὶ τῶν εἰδῶν αὐτῆς, ἥν τινα δύναμιν ἕκαστον ἔχει, καὶ
        πῶς δεῖ συνίστασθαι τοὺς μύθους [10] εἰ μέλλει καλῶς ἕξειν ἡ ποίησις, ἔτι δὲ ἐκ
        πόσων καὶ ποίων ἐστὶ μορίων, ὁμοίως δὲ καὶ περὶ τῶν ἄλλων ὅσα τῆς αὐτῆς ἐστι
        μεθόδου, λέγωμεν ἀρξάμενοι κατὰ φύσιν πρῶτον ἀπὸ τῶν πρώτων.
        Severity: Major
        Found in stories/stubs.js and 1 other location - About 1 hr to fix
        stories/stubs.js on lines 48..83

        Duplicated Code

        Duplicated code can lead to software that is hard to understand and difficult to change. The Don't Repeat Yourself (DRY) principle states:

        Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.

        When you violate DRY, bugs and maintenance problems are sure to follow. Duplicated code has a tendency to both continue to replicate and also to diverge (leaving bugs as two similar implementations differ in subtle ways).

        Tuning

        This issue has a mass of 59.

        We set useful threshold defaults for the languages we support but you may want to adjust these settings based on your project guidelines.

        The threshold configuration represents the minimum mass a code block must have to be analyzed for duplication. The lower the threshold, the more fine-grained the comparison.

        If the engine is too easily reporting duplication, try raising the threshold. If you suspect that the engine isn't catching enough duplication, try lowering the threshold. The best setting tends to differ from language to language.

        See codeclimate-duplication's documentation for more information about tuning the mass threshold in your .codeclimate.yml.

        Refactorings

        Further Reading

        Avoid too many return statements within this function.
        Open

          return false
        Severity: Major
        Found in src/decorators/GreekProsody.js - About 30 mins to fix

          Avoid too many return statements within this function.
          Open

                return syllables
          Severity: Major
          Found in src/decorators/GreekProsody.js - About 30 mins to fix

            Avoid too many return statements within this function.
            Open

                return syllables
            Severity: Major
            Found in src/decorators/GreekProsody.js - About 30 mins to fix

              Avoid too many return statements within this function.
              Open

                    return [...syllables, nextEl]
              Severity: Major
              Found in src/decorators/GreekProsody.js - About 30 mins to fix

                Function isLongByPosition has a Cognitive Complexity of 6 (exceeds 5 allowed). Consider refactoring.
                Open

                export const isLongByPosition = (syllable: string, nextSyllable: string): boolean => {
                  if (!nextSyllable) {
                    return false
                  }
                
                
                Severity: Minor
                Found in src/decorators/GreekProsody.js - About 25 mins to fix

                Cognitive Complexity

                Cognitive Complexity is a measure of how difficult a unit of code is to intuitively understand. Unlike Cyclomatic Complexity, which determines how difficult your code will be to test, Cognitive Complexity tells you how difficult your code will be to read and comprehend.

                A method's cognitive complexity is based on a few simple rules:

                • Code is not considered more complex when it uses shorthand that the language provides for collapsing multiple statements into one
                • Code is considered more complex for each "break in the linear flow of the code"
                • Code is considered more complex when "flow breaking structures are nested"

                Further reading

                Extra semicolon.
                Open

                import { configure } from 'enzyme';
                Severity: Minor
                Found in testSetup.js by eslint

                require or disallow semicolons instead of ASI (semi)

                JavaScript is unique amongst the C-like languages in that it doesn't require semicolons at the end of each statement. In many cases, the JavaScript engine can determine that a semicolon should be in a certain spot and will automatically add it. This feature is known as automatic semicolon insertion (ASI) and is considered one of the more controversial features of JavaScript. For example, the following lines are both valid:

                var name = "ESLint"
                var website = "eslint.org";

                On the first line, the JavaScript engine will automatically insert a semicolon, so this is not considered a syntax error. The JavaScript engine still knows how to interpret the line and knows that the line end indicates the end of the statement.

                In the debate over ASI, there are generally two schools of thought. The first is that we should treat ASI as if it didn't exist and always include semicolons manually. The rationale is that it's easier to always include semicolons than to try to remember when they are or are not required, and thus decreases the possibility of introducing an error.

                However, the ASI mechanism can sometimes be tricky to people who are using semicolons. For example, consider this code:

                return
                {
                    name: "ESLint"
                };

                This may look like a return statement that returns an object literal, however, the JavaScript engine will interpret this code as:

                return;
                {
                    name: "ESLint";
                }

                Effectively, a semicolon is inserted after the return statement, causing the code below it (a labeled literal inside a block) to be unreachable. This rule and the [no-unreachable](no-unreachable.md) rule will protect your code from such cases.

                On the other side of the argument are those who says that since semicolons are inserted automatically, they are optional and do not need to be inserted manually. However, the ASI mechanism can also be tricky to people who don't use semicolons. For example, consider this code:

                var globalCounter = { }
                
                (function () {
                    var n = 0
                    globalCounter.increment = function () {
                        return ++n
                    }
                })()

                In this example, a semicolon will not be inserted after the first line, causing a run-time error (because an empty object is called as if it's a function). The [no-unexpected-multiline](no-unexpected-multiline.md) rule can protect your code from such cases.

                Although ASI allows for more freedom over your coding style, it can also make your code behave in an unexpected way, whether you use semicolons or not. Therefore, it is best to know when ASI takes place and when it does not, and have ESLint protect your code from these potentially unexpected cases. In short, as once described by Isaac Schlueter, a \n character always ends a statement (just like a semicolon) unless one of the following is true:

                1. The statement has an unclosed paren, array literal, or object literal or ends in some other way that is not a valid way to end a statement. (For instance, ending with . or ,.)
                2. The line is -- or ++ (in which case it will decrement/increment the next token.)
                3. It is a for(), while(), do, if(), or else, and there is no {
                4. The next line starts with [, (, +, *, /, -, ,, ., or some other binary operator that can only be found between two tokens in a single expression.

                Rule Details

                This rule enforces consistent use of semicolons.

                Options

                This rule has two options, a string option and an object option.

                String option:

                • "always" (default) requires semicolons at the end of statements
                • "never" disallows semicolons as the end of statements (except to disambiguate statements beginning with [, (, /, +, or -)

                Object option:

                • "omitLastInOneLineBlock": true ignores the last semicolon in a block in which its braces (and therefore the content of the block) are in the same line

                always

                Examples of incorrect code for this rule with the default "always" option:

                /*eslint semi: ["error", "always"]*/
                
                var name = "ESLint"
                
                object.method = function() {
                    // ...
                }

                Examples of correct code for this rule with the default "always" option:

                /*eslint semi: "error"*/
                
                var name = "ESLint";
                
                object.method = function() {
                    // ...
                };

                never

                Examples of incorrect code for this rule with the "never" option:

                /*eslint semi: ["error", "never"]*/
                
                var name = "ESLint";
                
                object.method = function() {
                    // ...
                };

                Examples of correct code for this rule with the "never" option:

                /*eslint semi: ["error", "never"]*/
                
                var name = "ESLint"
                
                object.method = function() {
                    // ...
                }
                
                var name = "ESLint"
                
                ;(function() {
                    // ...
                })()

                omitLastInOneLineBlock

                Examples of additional correct code for this rule with the "always", { "omitLastInOneLineBlock": true } options:

                /*eslint semi: ["error", "always", { "omitLastInOneLineBlock": true}] */
                
                if (foo) { bar() }
                
                if (foo) { bar(); baz() }

                When Not To Use It

                If you do not want to enforce semicolon usage (or omission) in any particular way, then you can turn this rule off.

                Further Reading

                Related Rules

                • [no-extra-semi](no-extra-semi.md)
                • [no-unexpected-multiline](no-unexpected-multiline.md)
                • [semi-spacing](semi-spacing.md) Source: http://eslint.org/docs/rules/

                Extra semicolon.
                Open

                import Adapter from 'enzyme-adapter-react-16';
                Severity: Minor
                Found in testSetup.js by eslint

                require or disallow semicolons instead of ASI (semi)

                JavaScript is unique amongst the C-like languages in that it doesn't require semicolons at the end of each statement. In many cases, the JavaScript engine can determine that a semicolon should be in a certain spot and will automatically add it. This feature is known as automatic semicolon insertion (ASI) and is considered one of the more controversial features of JavaScript. For example, the following lines are both valid:

                var name = "ESLint"
                var website = "eslint.org";

                On the first line, the JavaScript engine will automatically insert a semicolon, so this is not considered a syntax error. The JavaScript engine still knows how to interpret the line and knows that the line end indicates the end of the statement.

                In the debate over ASI, there are generally two schools of thought. The first is that we should treat ASI as if it didn't exist and always include semicolons manually. The rationale is that it's easier to always include semicolons than to try to remember when they are or are not required, and thus decreases the possibility of introducing an error.

                However, the ASI mechanism can sometimes be tricky to people who are using semicolons. For example, consider this code:

                return
                {
                    name: "ESLint"
                };

                This may look like a return statement that returns an object literal, however, the JavaScript engine will interpret this code as:

                return;
                {
                    name: "ESLint";
                }

                Effectively, a semicolon is inserted after the return statement, causing the code below it (a labeled literal inside a block) to be unreachable. This rule and the [no-unreachable](no-unreachable.md) rule will protect your code from such cases.

                On the other side of the argument are those who says that since semicolons are inserted automatically, they are optional and do not need to be inserted manually. However, the ASI mechanism can also be tricky to people who don't use semicolons. For example, consider this code:

                var globalCounter = { }
                
                (function () {
                    var n = 0
                    globalCounter.increment = function () {
                        return ++n
                    }
                })()

                In this example, a semicolon will not be inserted after the first line, causing a run-time error (because an empty object is called as if it's a function). The [no-unexpected-multiline](no-unexpected-multiline.md) rule can protect your code from such cases.

                Although ASI allows for more freedom over your coding style, it can also make your code behave in an unexpected way, whether you use semicolons or not. Therefore, it is best to know when ASI takes place and when it does not, and have ESLint protect your code from these potentially unexpected cases. In short, as once described by Isaac Schlueter, a \n character always ends a statement (just like a semicolon) unless one of the following is true:

                1. The statement has an unclosed paren, array literal, or object literal or ends in some other way that is not a valid way to end a statement. (For instance, ending with . or ,.)
                2. The line is -- or ++ (in which case it will decrement/increment the next token.)
                3. It is a for(), while(), do, if(), or else, and there is no {
                4. The next line starts with [, (, +, *, /, -, ,, ., or some other binary operator that can only be found between two tokens in a single expression.

                Rule Details

                This rule enforces consistent use of semicolons.

                Options

                This rule has two options, a string option and an object option.

                String option:

                • "always" (default) requires semicolons at the end of statements
                • "never" disallows semicolons as the end of statements (except to disambiguate statements beginning with [, (, /, +, or -)

                Object option:

                • "omitLastInOneLineBlock": true ignores the last semicolon in a block in which its braces (and therefore the content of the block) are in the same line

                always

                Examples of incorrect code for this rule with the default "always" option:

                /*eslint semi: ["error", "always"]*/
                
                var name = "ESLint"
                
                object.method = function() {
                    // ...
                }

                Examples of correct code for this rule with the default "always" option:

                /*eslint semi: "error"*/
                
                var name = "ESLint";
                
                object.method = function() {
                    // ...
                };

                never

                Examples of incorrect code for this rule with the "never" option:

                /*eslint semi: ["error", "never"]*/
                
                var name = "ESLint";
                
                object.method = function() {
                    // ...
                };

                Examples of correct code for this rule with the "never" option:

                /*eslint semi: ["error", "never"]*/
                
                var name = "ESLint"
                
                object.method = function() {
                    // ...
                }
                
                var name = "ESLint"
                
                ;(function() {
                    // ...
                })()

                omitLastInOneLineBlock

                Examples of additional correct code for this rule with the "always", { "omitLastInOneLineBlock": true } options:

                /*eslint semi: ["error", "always", { "omitLastInOneLineBlock": true}] */
                
                if (foo) { bar() }
                
                if (foo) { bar(); baz() }

                When Not To Use It

                If you do not want to enforce semicolon usage (or omission) in any particular way, then you can turn this rule off.

                Further Reading

                Related Rules

                • [no-extra-semi](no-extra-semi.md)
                • [no-unexpected-multiline](no-unexpected-multiline.md)
                • [semi-spacing](semi-spacing.md) Source: http://eslint.org/docs/rules/

                Extra semicolon.
                Open

                configure({ adapter: new Adapter() });
                Severity: Minor
                Found in testSetup.js by eslint

                require or disallow semicolons instead of ASI (semi)

                JavaScript is unique amongst the C-like languages in that it doesn't require semicolons at the end of each statement. In many cases, the JavaScript engine can determine that a semicolon should be in a certain spot and will automatically add it. This feature is known as automatic semicolon insertion (ASI) and is considered one of the more controversial features of JavaScript. For example, the following lines are both valid:

                var name = "ESLint"
                var website = "eslint.org";

                On the first line, the JavaScript engine will automatically insert a semicolon, so this is not considered a syntax error. The JavaScript engine still knows how to interpret the line and knows that the line end indicates the end of the statement.

                In the debate over ASI, there are generally two schools of thought. The first is that we should treat ASI as if it didn't exist and always include semicolons manually. The rationale is that it's easier to always include semicolons than to try to remember when they are or are not required, and thus decreases the possibility of introducing an error.

                However, the ASI mechanism can sometimes be tricky to people who are using semicolons. For example, consider this code:

                return
                {
                    name: "ESLint"
                };

                This may look like a return statement that returns an object literal, however, the JavaScript engine will interpret this code as:

                return;
                {
                    name: "ESLint";
                }

                Effectively, a semicolon is inserted after the return statement, causing the code below it (a labeled literal inside a block) to be unreachable. This rule and the [no-unreachable](no-unreachable.md) rule will protect your code from such cases.

                On the other side of the argument are those who says that since semicolons are inserted automatically, they are optional and do not need to be inserted manually. However, the ASI mechanism can also be tricky to people who don't use semicolons. For example, consider this code:

                var globalCounter = { }
                
                (function () {
                    var n = 0
                    globalCounter.increment = function () {
                        return ++n
                    }
                })()

                In this example, a semicolon will not be inserted after the first line, causing a run-time error (because an empty object is called as if it's a function). The [no-unexpected-multiline](no-unexpected-multiline.md) rule can protect your code from such cases.

                Although ASI allows for more freedom over your coding style, it can also make your code behave in an unexpected way, whether you use semicolons or not. Therefore, it is best to know when ASI takes place and when it does not, and have ESLint protect your code from these potentially unexpected cases. In short, as once described by Isaac Schlueter, a \n character always ends a statement (just like a semicolon) unless one of the following is true:

                1. The statement has an unclosed paren, array literal, or object literal or ends in some other way that is not a valid way to end a statement. (For instance, ending with . or ,.)
                2. The line is -- or ++ (in which case it will decrement/increment the next token.)
                3. It is a for(), while(), do, if(), or else, and there is no {
                4. The next line starts with [, (, +, *, /, -, ,, ., or some other binary operator that can only be found between two tokens in a single expression.

                Rule Details

                This rule enforces consistent use of semicolons.

                Options

                This rule has two options, a string option and an object option.

                String option:

                • "always" (default) requires semicolons at the end of statements
                • "never" disallows semicolons as the end of statements (except to disambiguate statements beginning with [, (, /, +, or -)

                Object option:

                • "omitLastInOneLineBlock": true ignores the last semicolon in a block in which its braces (and therefore the content of the block) are in the same line

                always

                Examples of incorrect code for this rule with the default "always" option:

                /*eslint semi: ["error", "always"]*/
                
                var name = "ESLint"
                
                object.method = function() {
                    // ...
                }

                Examples of correct code for this rule with the default "always" option:

                /*eslint semi: "error"*/
                
                var name = "ESLint";
                
                object.method = function() {
                    // ...
                };

                never

                Examples of incorrect code for this rule with the "never" option:

                /*eslint semi: ["error", "never"]*/
                
                var name = "ESLint";
                
                object.method = function() {
                    // ...
                };

                Examples of correct code for this rule with the "never" option:

                /*eslint semi: ["error", "never"]*/
                
                var name = "ESLint"
                
                object.method = function() {
                    // ...
                }
                
                var name = "ESLint"
                
                ;(function() {
                    // ...
                })()

                omitLastInOneLineBlock

                Examples of additional correct code for this rule with the "always", { "omitLastInOneLineBlock": true } options:

                /*eslint semi: ["error", "always", { "omitLastInOneLineBlock": true}] */
                
                if (foo) { bar() }
                
                if (foo) { bar(); baz() }

                When Not To Use It

                If you do not want to enforce semicolon usage (or omission) in any particular way, then you can turn this rule off.

                Further Reading

                Related Rules

                • [no-extra-semi](no-extra-semi.md)
                • [no-unexpected-multiline](no-unexpected-multiline.md)
                • [semi-spacing](semi-spacing.md) Source: http://eslint.org/docs/rules/
                Severity
                Category
                Status
                Source
                Language