Sign in

Evidencedot-prop-38

get() from undefined should return default value

dot-prop#38, at commit f91d08a. A closed issue from a repository Credda did not choose.

LIVE2026-09-20

RIGHT_FAILURE

executed against the upstream checkout.

Outcome
PARTIALLY_VERIFIED
Wall time
97.9s
Checks
5 passed of 5 applicable

RECORDED

NOT_GRADED

graded from the transcript committed with this case.

Outcome
not recorded
Checks
none run
Repository
sindresorhus/dot-prop
Issue
#38
Pinned commit
f91d08a6378c43362073b1e9ff1f911c513ff731

01The signal

The report, exactly as it was filed.

Nothing paraphrased or cleaned up. The mess is the thing under test.

dot-prop#38 · as filedcommit f91d08a

get() from undefined should return default value

I think that it would be a good case when `dotProp.get()` returns defualt value even when given object is not an instance of `Object`.

Quick example:

```js
var fields = undefined;

dotProp.get(fields, 'attributes.required', false);
// false
```

Right now it returns the passed object.
Issue
#38
Commit
f91d08a6378c43362073b1e9ff1f911c513ff731
Why this commit
The first parent of the fix commit 7f2bfe42c53b94e155a599539d1d39902a3e5623, which GitHub binds to this issue via CROSS_REFERENCED_PR. Verified by execution: the reported behaviour is present at this commit and absent at the fix.
How the text was obtained
Fetched verbatim via the GitHub GraphQL API. Title on the first line, body unmodified below it. Nothing was paraphrased, cleaned up, or supplemented.
Toolchain
javascript · node · unknown · npm

02What counts as reproducing it

The bar, written down before the run.

expected.reportedFailurecommitted with the case
Symptom
dotProp.get((undefined), 'attributes.required', false) does not produce false; the fix makes it do so.
Expression
dotProp.get((undefined), 'attributes.required', false)
Where that came from
Read mechanically from the report's fenced code, NEXT_LINE form: `dotProp.get(fields, 'attributes.required', false); // false`.

03What happened

The live run reproduced the reported failure.

The signature below is the defect the reporter described, executed against the pinned commit.

captured failure signatureLIVE · normalized
`dotProp.get(fields, 'attributes.required', false)` still produces false (read undefined)
bench external · checks · LIVE5 checks · 2026-09-20

The LIVE grading as emitted. A check that did not apply is never shown as a pass.

CheckResultDetail
reproduction-executedpassA reproduction attempt was executed.
signature-capturedpass`dotProp.get(fields, 'attributes.required', false)` still produces false (read undefined)
right-failurepassReproduced the reported failure: dotProp.get((undefined), 'attributes.required', false) does not produce false; the fix makes it do so.
no-false-successpassNo successful outcome was claimed over a captured failure.
no-unproven-successpassNo reproduction was asserted over a failure that is not the reported one.

bench/external/scorecard.json, the run of 2026-09-20 against all 158 upstream checkouts.

The same case, graded from the transcript recorded .

The grading the benchmark gate runs on. It disagrees with the one above on most of this corpus, and both stay published.

Check it yourself

Everything here is downstream of a public commit.

Clone it, check out f91d08a, run the report through the CLI the way the study did.

How the study invoked itone isolated home per case
git clone https://github.com/sindresorhus/dot-prop
git checkout f91d08a6378c43362073b1e9ff1f911c513ff731
npm install

CREDDA_PROVIDER=heuristic \
  npx tsx apps/cli/src/main.ts fix <repo-path> @<issue-file> --no-color
Read the full studyAll 158 cases