Nice work Oliy. I especially liked the re-frame section as I work at Day8
on re-frame. I liked what you did with the HTTP handler, much cleaner :)
On Fri, Nov 11, 2016 at 1:15 AM Oliver Hine wrote:
> Hi Erik,
>
> One of the philosophies of Martian was that it was not a "closed" system
> so that
Hi Erik,
One of the philosophies of Martian was that it was not a "closed" system so
that it made no demands on the server, and you can use it with servers that
aren't yours and can't be changed. What you're describing is very much
server-side testing, so Martian doesn't help directly there.
H
Hi Oliy,
In some ways this resonates with a thought I’ve had for a while, which sort of
appeared while working on a spring-boot application in java.
So in Spring-boot, you have classes annotated as controllers, methods annotated
as request handlers which indicate what params and such they take
Hi all,
I wrote a blog post on some more advanced use of Martian, a library for
abstracting HTTP integration with other systems.
All these use cases leverage the fact that Martian separates your data (the
*what*) from the HTTP implementation details (the *how*) and lets you get
on with connect
