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
At the rest branch we currently are tracking implementation and functionality of the routes, this file specifically.
I will publish a package soon but there's some things I need to finalize first, but if anyone would like to help test route functions by actually writing a code example for them and testing practically with a real token, that would be appreciated. I doubt any routes will fail and if the types were wrong, that's on discord-api-types and not us.
The text was updated successfully, but these errors were encountered:
As outlined in that file, everyone should ensure full functionality of all endpoints before they get checked off. However it wouldn't be a bad idea to set up a file that will run through all API routes and test every one of them all at once. Opinions on setting this up?
However it wouldn't be a bad idea to set up a file that will run through all API routes and test every one of them all at once. Opinions on setting this up?
i thought about that, and it would be extremely cool if we could pull off unit tests for the rest api, but that just seems like a huge task to me. maybe it isn't; and if we did do it, we would have a cool line of saying "unit tested against the api". maybe re-look into it once bun's fetch/event loop bug gets fixed, and we can use bun's testing utils or just a standalone program in a test folder or something.
At the
rest
branch we currently are tracking implementation and functionality of the routes, this file specifically.I will publish a package soon but there's some things I need to finalize first, but if anyone would like to help test route functions by actually writing a code example for them and testing practically with a real token, that would be appreciated. I doubt any routes will fail and if the types were wrong, that's on
discord-api-types
and not us.The text was updated successfully, but these errors were encountered: