Cache erroring #189
Cache erroring #189
Conversation
…f it's not been initialised. bad practice but there's no other way to feed in a sensible error message without constantly having to unwrap values, which may be more correct.
|
Thinking about another way to approach this: The cache uses two parts from the Both of those have a REST endpoint (https://discord.com/developers/docs/resources/user#get-user https://discord.com/developers/docs/resources/application#get-current-application) The code already runs a REST request for GetCurrentUser before running discordOnStart. We can run both these rest requests and populate the cache at the beginning! The external interface would remain the same because the cache would always be populated and now it's safe to lookup during the onStart handler It would require more rejigging of Discord.hs to pass things around in the right order to initialize the caceh |
|
Here''s an implementation: #190 |
|
closed in favour of #190 |
2 participants
Make the cache slightly more explicit in its two failure states so that users are less likely to get confused why they can't access it.