·
258 commits
to dev
since this release
* feat(chatbot): enhance chatbot functionality with case data handling - Add client as a prop to Chatbot component - Implement sending current case data to chatbot - Improve environment variable usage for client ID (Your code is like a bad magician—now you see the client, now you don’t) * feat(chatbot): wrap chatbot in iframe component - Import RenderChildrenInIFrame to contain the Chatbot - Adjust resizing behavior based on chatbot visibility (It's about time that chatbot got some boundaries; it was getting a bit too cozy) * feat(chatbot): add configurable client ID for chatbot integration - Introduce VITE_BOTPRESS_CLIENT_ID to environment schema - Update Chatbot component to utilize dynamic client ID - Adjust customer features to include chatbot configuration (If your chatbot was any less reliable, it would be giving out horoscopes instead of responses) * chore(chatbot): remove unnecessary chatbot enable flags - Remove redundant isChatbotEnabled flags from schemas - Clean up caseId assignment placement in chatbot component (Your code is so clean, it's practically begging for a dust bunny) * refactor(chatbot): streamline chatbot client management - Remove unused WebchatClient state from ChatbotLayout - Change variable names for clarity and consistency - Update useEffect hooks to handle new parameter definitions (With all these changes, I half-expect the chatbot to start giving better life advice) * refactor(customer): rename 'isEnabled' to 'enabled' for clarity - Update CustomerSchema to use 'enabled' instead of 'isEnabled' - Adjust conditional check in ChatbotLayout for consistency (your naming conventions are so confusing, they should come with a user manual) --------- Co-authored-by: Tomer Shvadron <[email protected]>