petergtz / alexa-journal Goto Github PK

Alexa won't explain as much.

In the first iteration this could keep a in-memory map[UserID]bool. Later we might want to persists this somewhere.

These are currently not consistent and it's possible that it's hard to use proper date in addEntry. And same in DeleteEntry

It should be possible to create utterances that allow for both and hopefully make it possible to use a more unified logic in the code for dates.

An error occurred and it can be found by grepping the logs for 4739111663495868

This should pave the way for CanFulfillIntentRequest. Only US so far. Blocked.

An error occurred and it can be found by grepping the logs for 3724427934598140041

An error occurred and it can be found by grepping the logs for 5577006791947779410

• Welche Eintraege gibt es im August 2006

Or maybe just use reprompt objects everywhere?

Fuzzy Search:

• https://github.com/lithammer/fuzzysearch
• https://github.com/schollz/closestmatch

Word stemmer

• https://github.com/dchest/stemmer

Index Search Engines

• https://github.com/go-ego/riot
• https://github.com/blevesearch/bleve

Test-Body

Should use some kind of companion object to SheetBasedTabularData that can understand its errors and translate them to a response.

Reason: we don't want to encode Alexa responses into the drive package, which should stay independent.

Then, JournalProvider's Get method can simply return an additional error and errorInterpeter that can be used for logging and Alexa's response respectively.

The same approach can be used for AddEntry, GetEntry etc.

Additional thoughts: main is the adapter layer that adapts the business domain (Journal) into Alexa speak. It must there also transform errors coming from Google interaction into Alexa speak. The companion object or whatever should therefore also live there.

An error occurred and it can be found by grepping the logs for 5577006791947779410

An error occurred and it can be found by grepping the logs for 4606018198686923411

An error occurred and it can be found by grepping the logs for 3056332746016649150

An error occurred and it can be found by grepping the logs for 605394647632969758

• Was war (heute) vor einem Jahr
• Was war (heute) vor 7 Monaten

An error occurred and it can be found by grepping the logs for 6129484611666145821

An error occurred and it can be found by grepping the logs for 6129484611666145821

An error occurred and it can be found by grepping the logs for 8603989663476771718

An error occurred and it can be found by grepping the logs for 837825985403119657

An error occurred and it can be found by grepping the logs for 8674665223082153551

Can use some kind of request ID, that can then be used to grep the logs for said request and see the stacktrace.

Alexa would then tell the user that this issue will be fixed as quickly as possible.

An error occurred and it can be found by grepping the logs for 8674665223082153551

Hopefully this will help matching.

An error occurred and it can be found by grepping the logs for 5577006791947779410

An error occurred and it can be found by grepping the logs for 6651414131918424343

An error occurred and it can be found by grepping the logs for 1687184559264975024

An error occurred and it can be found by grepping the logs for 5577006791947779410

An error occurred and it can be found by grepping the logs for 5577006791947779410

An error occurred and it can be found by grepping the logs for 8121576815539813105

An error occurred and it can be found by grepping the logs for 5577006791947779410

An error occurred and it can be found by grepping the logs for 8505906760983331750

An error occurred and it can be found by grepping the logs for 3510942875414458836

An error occurred and it can be found by grepping the logs for 788787457839692041