Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Intellisense-style autocomplete doesn't work for zustand/middleware #262

Closed
dai-shi opened this issue Dec 13, 2020 · 3 comments
Closed

Intellisense-style autocomplete doesn't work for zustand/middleware #262

dai-shi opened this issue Dec 13, 2020 · 3 comments

Comments

@dai-shi
Copy link
Member

dai-shi commented Dec 13, 2020

from: #248 (comment)

This is an issue to track the titled issue.
(I hope this will be resolved when TypeScript supports "exports" in package.json.)

@dai-shi
Copy link
Member Author

dai-shi commented Jul 30, 2021

Closing this as this is not actionable now. Let's re-open it when things change.
If anyone is interested, feel free to investigate it.

@dai-shi dai-shi closed this as completed Jul 30, 2021
@TurtIeSocks
Copy link

@dai-shi apologies for bumping a really old issue but I've noticed a small bug that might be related and wasn't sure if I should open a new issue or if I'm doing something incorrectly.

I have an older project I wrote in JS and is just a little too tedious to port entirely to TS, and I noticed that the intellisense doesn't seem to work when set and get (or only set) arguments are used when creating the store.

For example:
Creating this store:
Screenshot 2023-07-21 at 2 38 01 PM
Results in this intellisense:
Screenshot 2023-07-21 at 2 37 49 PM

But creating this store:
Screenshot 2023-07-21 at 2 38 12 PM
Results in no intellisense:
Screenshot 2023-07-21 at 2 38 27 PM

The results are the same for each scenario when wrapping the store with the persist middleware.

Version:
"zustand": "^4.3.9"

Zustand is imported like so (if it's helpful to know)

import { create } from 'zustand'
import { persist } from 'zustand/middleware'

Any suggestions?

Thank you for this wonderful lib! 🙏

@dai-shi
Copy link
Member Author

dai-shi commented Jul 21, 2023

Can you please open a new discussion (not a new issue)?

I'm not sure if there's anything we can do, but let's discuss there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants