Skip to content

Conversation

@ashwins1
Copy link

@ashwins1 ashwins1 commented Oct 9, 2015

Hi Steve,

As we discussed over email, I think Template Haskell would be a good fit for part of this project, namely the API you expose to the underlying Consul functions. Since this API is an extremely thin wrapper, and since several of your API functions used the exact same code to access the Consul client functions, I saw fit to replace the common pieces with TH code that will transform the necessary functions automatically.

I have confirmed that my branch compiles and passes the unit tests you have written.

Please let me know if you'd like me to write some more tests, or change any of my code stylistically.

Ashwin Siripurapu and others added 3 commits October 8, 2015 00:21
shim of the internal API. Have excised the old code, and am
working on determining the parse tree and constructing it
in TH.
Changed .cabal file to include template-haskell dependency.
Had to move some code around because TH requires that any arguments
to TH functions come from an import.
Deleting unused files.
@sseveran
Copy link
Member

Can you have a look at the test/build failures? https://travis-ci.org/alphaHeavy/consul-haskell/builds/84446673

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants