Commit 2f8c651
authored
Fix AI API key not persisted in cache (#39)
The AI API key has a json:"-" tag for security (to prevent exposure in API
responses), but this caused it to be excluded when caching ChatbotSettings.
After the first message, settings were served from cache with an empty API key,
causing subsequent AI requests to fail with "AI not configured" error.
Solution: Create a chatbotSettingsCache wrapper struct that explicitly includes
the API key when caching, similar to how whatsAppAccountCache handles the
AccessToken field.
Fixes #381 parent c3abcc5 commit 2f8c651
1 file changed
+17
-5
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
31 | 31 | | |
32 | 32 | | |
33 | 33 | | |
| 34 | + | |
| 35 | + | |
| 36 | + | |
| 37 | + | |
| 38 | + | |
| 39 | + | |
34 | 40 | | |
35 | 41 | | |
36 | 42 | | |
| |||
39 | 45 | | |
40 | 46 | | |
41 | 47 | | |
42 | | - | |
43 | | - | |
44 | | - | |
| 48 | + | |
| 49 | + | |
| 50 | + | |
| 51 | + | |
| 52 | + | |
45 | 53 | | |
46 | 54 | | |
47 | 55 | | |
| |||
56 | 64 | | |
57 | 65 | | |
58 | 66 | | |
59 | | - | |
60 | | - | |
| 67 | + | |
| 68 | + | |
| 69 | + | |
| 70 | + | |
| 71 | + | |
| 72 | + | |
61 | 73 | | |
62 | 74 | | |
63 | 75 | | |
| |||
0 commit comments