Hard to understand stashing behavior

[benwiley4000]

Description

I'm not sure if this is a bug or just a question, but I'm trying to understand the stashing behavior of lint-staged. I have typescript running as part of my config (via function with no used arguments), and I would expect that any unstaged changes would be stashed before typescript is run, then unstashed afterward. But I am getting type errors reported from files that aren't staged. So perhaps I've misunderstood exactly what lint-staged is stashing, and why.

Steps to reproduce

Stage a file with no type errors, don't stage another file that has type errors.

module.exports = {
    "/**/*.{ts,tsx}": ["eslint --max-warnings=0", () => "tsc"],
};

Environment

Windows 11, lint-staged 15.2.1

[iiroj]

Maybe it's not clear enough in the readme: only unstaged changes to partially staged files are stashed. This is because stashing everything is a lot slower, affecting especially big projects.

A file is partially staged when there are both staged and unstaged changes to it.

[benwiley4000]

I see thank you for clarifying. Perhaps it would be nice to have an option for this, as it would be very useful for running typescript. Le dim. 28 avr. 2024, 8 h 02 a.m., Iiro Jäppinen ***@***.***> a écrit :

…

Closed #1402 <#1402> as not planned. — Reply to this email directly, view it on GitHub <#1402 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADHOD3KIGUTZUMOOCKPJWI3Y7SGI5AVCNFSM6AAAAABFLRVUWSVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJSGYZTGOBZGE2DSNA> . You are receiving this because you authored the thread.Message ID: ***@***.***>