You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
VaultFunc returns itself on create that one is just odd. While axios does something similar [Link] it returns an instance interface it extend from. Which brings me to. This also means that after returning an instance. You can STILL call create according to type definition...
All vault function return the same interface. None of them are generic all of them return an any promise. This will not play nice with strict checks and no implicit any configs.
create? is optional which makes it potentially undefined. As such I have to do vault.create?({ /* [...] */ }) to avoid an error/warning. This feels awkward.
The text was updated successfully, but these errors were encountered:
Greetings,
The type definition in this client is rudimental. Types in question:
VaultFunc
returns itself oncreate
that one is just odd. While axios does something similar [Link] it returns an instance interface it extend from. Which brings me to. This also means that after returning an instance. You can STILL call create according to type definition...any
promise. This will not play nice with strict checks and no implicit any configs.create?
is optional which makes it potentially undefined. As such I have to dovault.create?({ /* [...] */ })
to avoid an error/warning. This feels awkward.The text was updated successfully, but these errors were encountered: