falsy values not persisted when using pick

[JimCronqvist]

Are you using Nuxt?

• [ ] Check this box if you encountered the issue using Nuxt and the included module.

Describe the bug

Falsy values are not persisted when using pick, but rather filtered away.

Relevant configuration:

persist: { pick: ['selectedIndex'] }

If the value for selectedIndex is 0, the selectedIndex would not be persisted.

From what I can see, this is caused by this line below which filters away falsy values. https://github.com/prazdevs/deep-pick-omit/blob/f71e364a33fd2eb1ce8c0e71b2788f4abe8cee67/src/index.ts#L29

Is it possible to retain those values instead? (probably doesn't matter, but Vuex did keep those and made the upgrade unexpected)

Happy to create a PR in that library for the actual change if it helps, but I wanted to check first unless this was intended behavior.

Thanks for all your work on the plugin!

Reproduction

n/a

System Info

n/a

Used Package Manager

yarn

Validations

• [X] Follow our Code of Conduct
• [X] Read the Contributing Guide.
• [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• [X] The provided reproduction is a minimal reproducible of the bug.

[prazdevs]

That's not really intended, check should be indeed more precise and only check for undefined, not falsy values. Feel free to open an issue / PR on the upstream repo. Just gotta make sure everything still works as expected 🫡