Good Strategy, Bad Strategy https://www.goodreads.com/book/show/11721966-good-strategy-b...
621 karma · joined September 12, 2011
Good Strategy, Bad Strategy https://www.goodreads.com/book/show/11721966-good-strategy-b...
Their FAQ is at https://assembly.com/help/basics
Short story, Gitter is awesome!
I tried to make them a lot more readable. :)
If you are talking about the code of the program, they wont be changed because, the program just compiles and executes the templates.
If I didnt answer your question properly, could you please elaborate?
Yes, sometimes I fail to make it. But it's a rule I want to live by.
This current program just a small step in the right direction. :)
EDIT: Currently, I have a test suite at https://github.com/pksunkara/alpaca/tree/testing which tests the generated client libraries of an example API with the respective server.
But, to do that I need a format using which people can define their API. I used JSON and only supported the elements that I needed to generate the client libraries.
Could you please link if something does it? From what I gather, the above mentioned sites only provide methods of describing the API and/or Automating the API on the server side. Nothing is said about client libraries.
Thanks
These will cover most of the APIs. And I am open to include other kind of authentication strategies too.
https://github.com/pksunkara/alpaca#authorization-strategies
EDIT: OAUTH Consumption is not the main priority here. The problem I intended to solve is automating the development and maintaing of API client libraries in several different languages.
That said, I intend to add support for OAUTH consumption too.
Please ask if you have any questions. Thanks