vkbansal/eslint-plugin-jsx-control-statements

Issues

• Enhancement: Enforce specific syntax for conditionals

  #9 opened 2 years ago by texttechne
  0

• jsx-jcs-no-undef triggers for globals like JSON or window

  #14 opened 2 years ago by texttechne
  6

• Optionally disallow deprecated <Else />

  #15 opened 2 years ago by stoikerty
  2

• Looking for maintainers

  #18 opened 2 years ago by vkbansal
  0

• jsx-use-if-tag should handle AND operator

  #22 opened 2 years ago by draperunner
  0

• Not playing well with airbnb rules

  #24 opened 2 years ago by libasoles
  0

• 'If' is not defined react/jsx-no-undef

  #25 opened 5 years ago by anilnamde
  3

• jsx-jcs-no-undef not catching missing components

  #17 opened 6 years ago by igl
  1

• Plugin won't run

  #11 opened 8 years ago by fredva
  9

• Extend jsx-jcs-no-undef to work with <With />

  #19 opened 7 years ago by martinmacko47
  5

• Is it possible to make the optionally linter warnings actually errors

  #16 opened 8 years ago by MichaelTaylor3D
  2

• Error: Cannot read property 'value' of undefined

  #12 opened 9 years ago by jurgob
  2

• Silent eslint for "each" attribute of "for" statement

  #1 opened 9 years ago by texttechne
  21

• Require index?

  #8 opened 9 years ago by texttechne
  2

• Multiple children supported

  #4 opened 9 years ago by texttechne
  4

• Error: Cannot read property 'value' of null

  #6 opened 9 years ago by vkbansal
  1

• Support <Choose>

  #3 opened 9 years ago by texttechne
  6

• Warn if <If> or <Else> or <For> are empty

  #2 opened 9 years ago by texttechne
  3