Get rid of the 'dynamics' and put all data in the trigger event tag (tupple api)

[jappeace]

I believe this idea was discussed in a PR: #78

Today I tried making this a reality but I ran out of time. I do have an approach to make this work: we construct in the servant interpreting part a function that will create a Req from the tag that peels of layers of the tupple. If we create the function like that it can turn the tag into a Req in one go, so we don't have to 'combine' data from different events.

I started doing this but everything blew up and I realized most code had to change to make this work.
It does become a lot neater though if you do it like this I think.

[jappeace]

I'm working on this here: https://github.com/jappeace/servant-reflex/tree/tupple-api

[imalsogreg]

Thanks @jappeace ! I definitely like this approach. I have made some progress on it at https://github.com/imalsogreg/servant-reflex/tree/tuple-api-3 - may be work taking a look to see how I'm dealing with the nested tuples.

This approach has some confusing dark corners, but tuple-api-3 is very close to being releasable.

Happy to go instead with your thing, whether it's based on tuple-api-3 or not :)

[jappeace]

I'll use your approach then if I can make it work.

I just need this asap.

For now I merged master into it: https://github.com/jappeace/servant-reflex/tree/tuple-api-3
I'll continue another time.