Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • vidjil vidjil
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,721
    • Issues 1,721
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 86
    • Merge requests 86
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • vidjil
  • vidjilvidjil
  • Issues
  • #2921

Closed
Open
Created Nov 30, 2017 by Mikaël Salson@mikael-sOwner

JS : `==` ou `===` en comparant par rapport à `undefined` ou `0`

Dans #2272 (closed) @RyanHerb avait mis un fichier montrant que jshint râlait pour des == à la place de ===. Par exemple :

clone.js: line 46, col 27, Use '===' to compare with 'undefined'.
clone.js: line 68, col 35, Use '===' to compare with '0'.
clone.js: line 81, col 33, Use '!==' to compare with 'undefined'.
clone.js: line 100, col 18, Use '===' to compare with '0'.

@RyanHerb avait d'ailleurs fait des modifications dans ce sens : cc7595e2. Mais maintenant cela ne semble pas poser de problème à jshint : !139 (comment 65732)

Quelle est la bonne pratique à suivre ?

Edited Nov 30, 2017 by Mikaël Salson
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking