ksw5 / customui

Hey, y'all!

My name is Kieran! I am a flight attendant, dog mom, and Android Engineer who is passionate about creating great user experiences and solving problems.

• 📚 I’m currently learning Compose
• 🏀 I'm currently working on a group project NBA Game Ready app

🔧 Technologies & Tools

📈 Stats

customui's Issues

Quick options logic

customUI/app/src/main/java/com/example/customui/ui/ChatFragment.kt

Line 123 in 3c4a6c7

sendStatementToEngine(response.statement!!)

Quick options handling is not done as with a typed message.
every quick option has a "type" and a "kind" property which defines how the "statement" API should be constructed.
for "postback" option the API will be called with "...statement?postaback=...", while for statement it called with "...statement?statement=...". there's also an article typed option "statemet?articleId=..."
You can look at the StatementRequest class hierarchy for the available options.

You can use the StatementFactory.create(QuickOption) method to pass the right request.

Adding handling of quick options complicates the sample, but if the customer is using only the engine part, he should now about how the requests should be sent for each case.