Skip to content

Issue in return-in-computed-property & require-render-return #130

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

Closed
armano2 opened this issue Aug 4, 2017 · 0 comments · Fixed by #131
Closed

Issue in return-in-computed-property & require-render-return #130

armano2 opened this issue Aug 4, 2017 · 0 comments · Fixed by #131

Comments

@armano2
Copy link
Contributor

armano2 commented Aug 4, 2017

I tried to test new rules in one of my big projects and i have few false positive errors in case when there is CodePath/Function inside with no return.

Affected rules:

  • return-in-computed-property
  • require-render-return

Example of false positive error:

export default {
  computed: {
    foo () {
      const options = []
      this.matches.forEach((match) => {
        options.push(match)
      })
      return options
    }
  }
}
armano2 added a commit to armano2/eslint-plugin-vue that referenced this issue Aug 4, 2017
@armano2 armano2 changed the title Issue in return-in-computed-property Issue in return-in-computed-property & require-render-return Aug 4, 2017
@michalsnik michalsnik added this to the Official release milestone Aug 4, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants