-
Notifications
You must be signed in to change notification settings - Fork 3
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
chore: add error code constants #2
Conversation
I am a bit confused, as there is no such field in luv ( |
Oh right, that was a recent addition to Luv now that I think about it. I even PRed it into the docs. Hm regarding the values though I am indeed slightly concerned about system inconsistencies. I have been thinking on how to do this while: a) Document the exact field names. (So Do you have any ideas how to approach that? |
I think for now we will go with something like this 3069b62. Just an alias that has all the fields. Can you do this? Also use ---
---description here!
---
---@type uv.errno
uv.errno = {} |
Hey @Bilal2453 thanks for the response. Yep that makes total sense to me. I'll make those changes 👍 |
Hey @Bilal2453 I have made the updates. I have only used this in the context of Neovim. Here is what the completion looks like after the change:
I also removed some values, and used the values from
Let me know what you think |
thanks! |
I noticed errno is missing and added the values by running
errono -ls
on my Mac. I also addedUNKOWN
because I saw that when I inspected theuv.errno
table in Neovim.This has the same issue as constants in that the errno can change depending on the system, unix vs windows.