Well, It is kind of pain to wrap all these API’s, and the method I am using right now is relatively inefficient. This means, I will be completely re-working the structure in 0.2.0, and deprecating the 0.1.0.
The client core will be the same, but I will completely re-work the wrapper to use graphql to it’s fullest. It will only get you what you want and what you need, the docs essentially being your schema, and you write python instead of graphql. I am also planning on making a tool (schemagen) that will write the wrappers for me
Yes, it is a automatic replit client w/ an api wrapper. They are kind of the same thing, but api wrapper specifies that I made the graphql stuff easier to use by “wrapping” it in python, and the client suggests it sends working requests to replit.
@OmegaOrbitals just tested and it installs fine using git. The only hurtle is that replit’s git version was outdated, causing a GLIB_C error. (Ig you pretty much expect replit to be outdated in some parts)
You would fix this by adding pkgs.git to replit.nix
The first ever replit graphql lib that almost all the others were based off was made in node, so…
(Also, if you know me, you will know I am not a node.js person)