- Migrated documentation to rst, md was missing a lot of features and making it harder to do stuff
- Merged @era automatic camelCase conversion
- Finally go some time to write it's documentation, and now we have support for serializers. For now, only for deserializations.
We are very close to launching version 1
Documentation on how to make new flavours available here: http://tapioca-wrapper.readthedocs.org/en/latest/newflavour.html
This is ready for version 1.0, so it contains references to code it is not yet on pip
Use the
stable docs for the current version on pip
Thanks! I'm planning to make a client for this simple API http://api.citybik.es/v2/ and I was wondering if it was worthwhile to make a Tapioca wrapper for it. But right now I'm realizing how simple it is(here is a Ruby wrapper) and finding about the Request package I'm pretty sure it isn't really worthwhile.
Unless I'm missing something awesome about Tapioca?
well, Tapioca more than requests, actually, it uses requests. First you will have autocompletion for you endpoints when working in a ipython-like shell. You can get the data already in the correct type, as Python objects, you can make easier the configuration proccess..
you can take a look here: https://ep2015.europython.eu/conference/talks/what-is-wrong-with-api-wrappers-and-how-can-we-do-better
And others will be abe able to easily download your project and use it (considering you are going to upload it to pip)
Hey, I want to use tapioca to write a client for the ThingWorx API. But I'm confused about the auth mechanism. I want to use an application-key, but I don't understand the options oauth2/1 or basic_auth. Should I use none of the provided auth options and pass a custom header? Because that's how I do it when I'm using the requests module.
I’m developing a new flavour https://github.com/medeirosthiago/tapioca-desk
but I have no idea how to create the tests :worried:
I took a look on some others flavours but couldn’t figure this out by myself
Ideally you have a test account and make real requests to verify if things are working properly. But this is hard to do and it's easy to get false positives in the process due to any kind of temporary problems in the service
Because of that, unless it's a critical integration I tend not to test this kind of things
I was having a hard time trying to figure this out :P
I'm an experienced developer, tho. So, while I'll be struggling to meet Python's specific quality standards, I'm used to software development as an activity
Question: is there any alternative example of how to create a flavour that does not use cookiecutter? I'm reading "Build a Wrapper" but I can't find a proper documentation of how to do it. https://tapioca-wrapper.readthedocs.io/en/stable/buildingawrapper.html
I'm mostly reading the source code of existing wrappers - but it's clearly not as productive as it could be
Let me know if you have some trouble with some specific part, happy to help