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
I think the fewer method you have of solving stuff then the easier it is to maintain.
it would also reduce the amount of documentation needed. making it easer to learn
if everyone where enforced to use the async methods then the easier it would also be to swap it out for something else like a database where the only possibility is to use async network IO or like a spec'ed CookieStore that is only async
Not saying you should rip out the functionality...
just remove the documentation around sync usage
update the examples to use async/await
add like a jsdoc with @depricated
The text was updated successfully, but these errors were encountered:
At a minimum, all APIs that return a promise should be changed to async functions, so that they are guaranteed to only resolve/reject, not resolve/reject/throw.
I think the fewer method you have of solving stuff then the easier it is to maintain.
it would also reduce the amount of documentation needed. making it easer to learn
if everyone where enforced to use the async methods then the easier it would also be to swap it out for something else like a database where the only possibility is to use async network IO or like a spec'ed CookieStore that is only async
Not saying you should rip out the functionality...
async/await
@depricated
The text was updated successfully, but these errors were encountered: