Closed ysangkok closed 5 years ago
FYI (we should probably add this to the README) this library cannot currently be used as a gitlib via tools-deps because most of the API is auto-generated at build time from the devtools protocol spec.
We don't think we actually need to ship the devtools-protocols if we generate all required code in the command namespaces. I could get rid of the submodule. This needs some work.
I want to support deps.edn usage as I think it is important for the future (and I personally like using git coordinates for libraries)
There's new code in master which generates the command namespaces fully (the specs and function defs are part of the code, not simply a macro call).
If this approach works, then the devtools-protocol files aren't needed at runtime anymore. The latest commit has tests passing, but I haven't tested it at all in real use yet.
works great now, tested with 58a396f54f469e98b5aae92b9357d65434914228
I have the following in my
deps.edn
: