## The Problem
How can I build libraries and modules that operate accross programming
languages and environments?
## The Solution
To solve this problem with web services, we build APIs that we can use between
languages. Unfortunately, these APIs require us to make HTTP requests.
...or do they?
Enter GraphQL: Protocal Agnostic, that means, we can implement it over a CLI
interface and have an incredibly handy way to build cross language bindings
without all the fuss.
## What does it do?
libgql will define a protocal for doing graphql over CLI and implement as many
language bindings as we possibly can.
## Usage
I would recommend looking at the tests for usage, since it varies from language
to language. To consume a module that uses libgql, install the bindings for your
language:
| javascript | `yarn add libgql` |
|------------|-------------------------|
| python | `pipenv install libgql` |
Then import the bindings and load the module:
### javascript
```javascript
import { loadModule } from "libgql"
const myModule = loadModule("./path/to/libgql/module/executable");
result = await myModule(graphqlQueryStringHere, optionalVariables);
```
### python
```python
from "libgql" import load_module
myModule = load_module("./path/to/libgql/module/executable")
result = myModule(graphqlQueryStringHere, optionalVariables)
```
Metadata
Release files for libgql 0.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| libgql-0.0.1.tar.gz | 3.5 kB | Without provenance | Details |
Release files / libgql-0.0.1.tar.gz
| Download URL | libgql-0.0.1.tar.gz |
|---|---|
| Size | 3.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f643f3472571250958df74389a3548b6d1d5870140fba7c25a3fbbfc112cff9e
|
|
BLAKE2b-256 checksum How to use checksums |
78daa02b1988cbefa46e0ca97e02c3150e26b19e6c8071836f41d47cd5b11699
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for libgql 0.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.