-
Notifications
You must be signed in to change notification settings - Fork 7
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
Make consume
and ContextConsumer
return undefined
rather than null
#31
Make consume
and ContextConsumer
return undefined
rather than null
#31
Conversation
🦋 Changeset detectedLatest commit: a894999 The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
@boris-petrov what TypeScript errors are you seeing? When I run it locally I see a few warnings: But they were before - nothing related to your changes. There are no errors and the linting passes correctly. |
Well, running
And below there's a lot more. One of them:
That doesn't happen when you clone the repo, |
@boris-petrov I am not seeing those on my machine! What versions of node and npm are you on? |
Node v22.8.0, npm 10.8.3. I don't think these should matter in that case though. |
@boris-petrov I can't seem to reproduce what you're seeing. You said you weren't sure if your changes are correct - does this mean running |
No, the same thing happens on |
We can definitely add some tests! It would make sense to add a test case in each to test what the result is when no provider is present. Would you like to add those? |
Sorry for the delay. I’ll try to do that end of next week.
Message ID: ***@***.***>
|
910114e
to
11cfe33
Compare
@kevinkucharczyk I've added two tests for the two changes. I also found why I was getting these errors. Apparently one must build an addon before one can use it. 😄 Didn't know that. So once I ran |
Fixes #29
cc @kevinkucharczyk
I'm not sure I've done the change correctly - running
npm lint
locally seems to lead to a lot of TypeScript errors which I'm unsure how to fix. Please take a look and let me know if I've done something wrong.