_.isInteger([1]) returns true

Open
#252 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
tooling

Research direction

Start by locating isNumeric and its callers, isInteger and isFloat, then reproduce the array examples from the issue. Done means single-element arrays are rejected by both predicates while ordinary integer and float inputs continue to work.

Written by the indexing model from the issue text.

Description

breaking change bug

There is an issue with the function predictates isInteger() and isFloat() where a number is passed in an array of length 1.

eg:

_.isInteger([1])
// true
_.isFloat([1.1])
// true
// both should be false.

The fix for this should be pretty easy by just adding if (i === undefined || i === null || i instanceof Array) return false to the top of isNumeric.

This simple gate will block undefined, null and array.

Suggestions?

Dominant language
JavaScript
Stars
622
Forks
114
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from documentcloud/underscore-contrib

All issues in documentcloud/underscore-contrib

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.