Skip to content

Repository files navigation

README

This repo is a simple client for the GitHub Rest V3 API.

I didn't find a full API on one page, so I gathered it from many pages. You might have to put API details into a JSON file yourself. Check out api.json to see how.

You can find the documents here.

How to Use

Please refer to ./example

Dependencies

I use yason for json parser, dexador for http client.

Install

This repo has already been deployed to quicklisp. You can simply use (ql:quickload "github-api-cl") to install it.

Read api.json file

Suppose we have api.json looks like:

{
"repositories": {
"repositories": {
"List repositories for a user": {
"parameters": [
["type", "string"],
["sort","string"],
["direction","string"]
],
"api": "GET /users/:username/repos",
"link": "https://developer.github.com/v3/repos/#list-repositories-for-a-user"
}
}
}
}

Examples:

;; load system first
(ql:quickload "github-api-cl")
;; read api.json in this repo, path var is github-api-doc::*api-json-file-path*
(github-api-doc:read-api-json) ;; => return a hashtable of this json;; OR you can give path specially
(github-api-doc:read-api-json #P"/path/to/api.json")

Generate api instance

After read api.json file, you can generate api instance by using github-api-doc:make-api-doc-from-json

Examples:

;; read api.json
(defparameter*api-docs* (github-api-doc:read-api-json))
;; &rest arguments are the steps of reading json
(defparameter*api-doc* (github-api-doc:make-api-doc-from-json *api-docs*"repositories""repositories""List repositories for a user"))
;; Get api-doc: ;;api-doc object:;; api: GET /users/:username/repos,;; http method: GET,;; slots: (:username),;; fmt-control: (/users/~a/repos);; parameters: ((type string) (sort string) (direction string));; OR, you can make instance manually
(setf*api-doc* (make-instance'api-doc
:api"GET /users/:username/repos":parameters'(("type""string") ("sort""string") ("direction""string")))

The api.json file is very flexible as it's just a JSON file. You don't have to stick to the GitHub API structure if you don't want to. The only part that github-api-cl is concerned with is this section:

{
"parameters": [
["type", "string"],
["sort","string"],
["direction","string"]
],
"api": "GET /users/:username/repos",
}

You can read this json file and (github-api-doc:make-api-doc-from-json (github-api-doc:read-api-json #P"this-simple-api.json"))

Make github-api client

Making github-api client:

;; make instance of api-client
(defparameter*client-without-token* (make-instance'github-client:api-client))
;; if you have token for github rest api call, make like this
(defparameter*client-with-token* (make-instance'github-client:api-client :token"123"))

Call api

With client and api, now we can call api in our code:

;; call api with client and api we made before
(github-client:github-api-call *client-without-token**api-doc*)
;;; REPL will ask you to input `:username`, `type`, `sort`, and `direction`;;; Then, it will return the dex:http-response, you can find this MULTIPLE-VALUEs ;;; return format in https://github.com/fukamachi/dexador#following-redirects-get-or-head;; call POST method api with additional :content keyword
(github-client:github-api-call *client-without-token**api-doc*:headers'((header0 . value0) (header1 . value1))
:content"this argument pass to dexador directly")

github-api-call will call api with the default headers '(("Accept" . "application/vnd.github+json")). Any other headers pass to :headers will been added ("Accept" . "application/vnd.github+json").

From now, github-api-cl's job is done, left all http response back to you, you can do whatever you want.

Wait, if you do not want REPL ask you to input every slots and parameters:

(github-client:github-api-call *client-without-token**api-doc*:username"lisp":type"public":direction"test":neither-slots-nor-parameter1) ;; last keyword is redundant

With keywords input, REPL won't ask you anything, just call https://api.github.com/users/lisp/repos?type=\"public\"&direction=\"test\".

As example shows, :username fills api slot, :type & :direction are used for parameters. Meanwhile :neither-slots-nor-parameter doesn't play any role in this API.

For POST method api, :content is the keyword for add the content. It pass to :content keyword of dexador's POSTmethod. Check ./example/github-gist-cl to find how to create the gist.

Authorization

Token, user-name, and passd

When you need authorization, you can include :token, :user-name and :passd in github-client:github-api-call as keywords.

Here's how it works:

  • If you input :token, will use token you provided
  • If no :token given but client has token already, it will use token stored in client
  • If neither :token nor client's token is given, but has :passd keyword, will use :user-name & passd as authorization. (I just assume you give :user-name too, when you give :passd)

About

Common Lisp Github REST API Client

Topics

Resources

Stars

18 stars

Watchers

3 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
GitHub - ccqpein/Github-API-CL: Common Lisp Github REST API Client · GitHub
Skip to content

Repository files navigation

README

This repo is a simple client for the GitHub Rest V3 API.

I didn't find a full API on one page, so I gathered it from many pages. You might have to put API details into a JSON file yourself. Check out api.json to see how.

You can find the documents here.

How to Use

Please refer to ./example

Dependencies

I use yason for json parser, dexador for http client.

Install

This repo has already been deployed to quicklisp. You can simply use (ql:quickload "github-api-cl") to install it.

Read api.json file

Suppose we have api.json looks like:

{
"repositories": {
"repositories": {
"List repositories for a user": {
"parameters": [
["type", "string"],
["sort","string"],
["direction","string"]
],
"api": "GET /users/:username/repos",
"link": "https://developer.github.com/v3/repos/#list-repositories-for-a-user"
}
}
}
}

Examples:

;; load system first
(ql:quickload "github-api-cl")
;; read api.json in this repo, path var is github-api-doc::*api-json-file-path*
(github-api-doc:read-api-json) ;; => return a hashtable of this json;; OR you can give path specially
(github-api-doc:read-api-json #P"/path/to/api.json")

Generate api instance

After read api.json file, you can generate api instance by using github-api-doc:make-api-doc-from-json

Examples:

;; read api.json
(defparameter*api-docs* (github-api-doc:read-api-json))
;; &rest arguments are the steps of reading json
(defparameter*api-doc* (github-api-doc:make-api-doc-from-json *api-docs*"repositories""repositories""List repositories for a user"))
;; Get api-doc: ;;api-doc object:;; api: GET /users/:username/repos,;; http method: GET,;; slots: (:username),;; fmt-control: (/users/~a/repos);; parameters: ((type string) (sort string) (direction string));; OR, you can make instance manually
(setf*api-doc* (make-instance'api-doc
:api"GET /users/:username/repos":parameters'(("type""string") ("sort""string") ("direction""string")))

The api.json file is very flexible as it's just a JSON file. You don't have to stick to the GitHub API structure if you don't want to. The only part that github-api-cl is concerned with is this section:

{
"parameters": [
["type", "string"],
["sort","string"],
["direction","string"]
],
"api": "GET /users/:username/repos",
}

You can read this json file and (github-api-doc:make-api-doc-from-json (github-api-doc:read-api-json #P"this-simple-api.json"))

Make github-api client

Making github-api client:

;; make instance of api-client
(defparameter*client-without-token* (make-instance'github-client:api-client))
;; if you have token for github rest api call, make like this
(defparameter*client-with-token* (make-instance'github-client:api-client :token"123"))

Call api

With client and api, now we can call api in our code:

;; call api with client and api we made before
(github-client:github-api-call *client-without-token**api-doc*)
;;; REPL will ask you to input `:username`, `type`, `sort`, and `direction`;;; Then, it will return the dex:http-response, you can find this MULTIPLE-VALUEs ;;; return format in https://github.com/fukamachi/dexador#following-redirects-get-or-head;; call POST method api with additional :content keyword
(github-client:github-api-call *client-without-token**api-doc*:headers'((header0 . value0) (header1 . value1))
:content"this argument pass to dexador directly")

github-api-call will call api with the default headers '(("Accept" . "application/vnd.github+json")). Any other headers pass to :headers will been added ("Accept" . "application/vnd.github+json").

From now, github-api-cl's job is done, left all http response back to you, you can do whatever you want.

Wait, if you do not want REPL ask you to input every slots and parameters:

(github-client:github-api-call *client-without-token**api-doc*:username"lisp":type"public":direction"test":neither-slots-nor-parameter1) ;; last keyword is redundant

With keywords input, REPL won't ask you anything, just call https://api.github.com/users/lisp/repos?type=\"public\"&direction=\"test\".

As example shows, :username fills api slot, :type & :direction are used for parameters. Meanwhile :neither-slots-nor-parameter doesn't play any role in this API.

For POST method api, :content is the keyword for add the content. It pass to :content keyword of dexador's POSTmethod. Check ./example/github-gist-cl to find how to create the gist.

Authorization

Token, user-name, and passd

When you need authorization, you can include :token, :user-name and :passd in github-client:github-api-call as keywords.

Here's how it works:

  • If you input :token, will use token you provided
  • If no :token given but client has token already, it will use token stored in client
  • If neither :token nor client's token is given, but has :passd keyword, will use :user-name & passd as authorization. (I just assume you give :user-name too, when you give :passd)

About

Common Lisp Github REST API Client

Topics

Resources

Stars

18 stars

Watchers

3 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Force GitHub README to respect dark mode (function() { var style = document.createElement('style'); style.textContent = ' .markdown-body { color-scheme: dark light; } .markdown-body pre { background: #161b22 !important; } .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; } .markdown-body table th, .markdown-body table td { border-color: #30363d !important; } .markdown-body img { background: #0d1117; } .markdown-body blockquote { border-left-color: #8b949e; } .markdown-body hr { border-color: #30363d; } '; document.head.appendChild(style); })(); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' GitHub - ccqpein/Github-API-CL: Common Lisp Github REST API Client · GitHub
Skip to content

Repository files navigation

README

This repo is a simple client for the GitHub Rest V3 API.

I didn't find a full API on one page, so I gathered it from many pages. You might have to put API details into a JSON file yourself. Check out api.json to see how.

You can find the documents here.

How to Use

Please refer to ./example

Dependencies

I use yason for json parser, dexador for http client.

Install

This repo has already been deployed to quicklisp. You can simply use (ql:quickload "github-api-cl") to install it.

Read api.json file

Suppose we have api.json looks like:

{
"repositories": {
"repositories": {
"List repositories for a user": {
"parameters": [
["type", "string"],
["sort","string"],
["direction","string"]
],
"api": "GET /users/:username/repos",
"link": "https://developer.github.com/v3/repos/#list-repositories-for-a-user"
}
}
}
}

Examples:

;; load system first
(ql:quickload "github-api-cl")
;; read api.json in this repo, path var is github-api-doc::*api-json-file-path*
(github-api-doc:read-api-json) ;; => return a hashtable of this json;; OR you can give path specially
(github-api-doc:read-api-json #P"/path/to/api.json")

Generate api instance

After read api.json file, you can generate api instance by using github-api-doc:make-api-doc-from-json

Examples:

;; read api.json
(defparameter*api-docs* (github-api-doc:read-api-json))
;; &rest arguments are the steps of reading json
(defparameter*api-doc* (github-api-doc:make-api-doc-from-json *api-docs*"repositories""repositories""List repositories for a user"))
;; Get api-doc: ;;api-doc object:;; api: GET /users/:username/repos,;; http method: GET,;; slots: (:username),;; fmt-control: (/users/~a/repos);; parameters: ((type string) (sort string) (direction string));; OR, you can make instance manually
(setf*api-doc* (make-instance'api-doc
:api"GET /users/:username/repos":parameters'(("type""string") ("sort""string") ("direction""string")))

The api.json file is very flexible as it's just a JSON file. You don't have to stick to the GitHub API structure if you don't want to. The only part that github-api-cl is concerned with is this section:

{
"parameters": [
["type", "string"],
["sort","string"],
["direction","string"]
],
"api": "GET /users/:username/repos",
}

You can read this json file and (github-api-doc:make-api-doc-from-json (github-api-doc:read-api-json #P"this-simple-api.json"))

Make github-api client

Making github-api client:

;; make instance of api-client
(defparameter*client-without-token* (make-instance'github-client:api-client))
;; if you have token for github rest api call, make like this
(defparameter*client-with-token* (make-instance'github-client:api-client :token"123"))

Call api

With client and api, now we can call api in our code:

;; call api with client and api we made before
(github-client:github-api-call *client-without-token**api-doc*)
;;; REPL will ask you to input `:username`, `type`, `sort`, and `direction`;;; Then, it will return the dex:http-response, you can find this MULTIPLE-VALUEs ;;; return format in https://github.com/fukamachi/dexador#following-redirects-get-or-head;; call POST method api with additional :content keyword
(github-client:github-api-call *client-without-token**api-doc*:headers'((header0 . value0) (header1 . value1))
:content"this argument pass to dexador directly")

github-api-call will call api with the default headers '(("Accept" . "application/vnd.github+json")). Any other headers pass to :headers will been added ("Accept" . "application/vnd.github+json").

From now, github-api-cl's job is done, left all http response back to you, you can do whatever you want.

Wait, if you do not want REPL ask you to input every slots and parameters:

(github-client:github-api-call *client-without-token**api-doc*:username"lisp":type"public":direction"test":neither-slots-nor-parameter1) ;; last keyword is redundant

With keywords input, REPL won't ask you anything, just call https://api.github.com/users/lisp/repos?type=\"public\"&direction=\"test\".

As example shows, :username fills api slot, :type & :direction are used for parameters. Meanwhile :neither-slots-nor-parameter doesn't play any role in this API.

For POST method api, :content is the keyword for add the content. It pass to :content keyword of dexador's POSTmethod. Check ./example/github-gist-cl to find how to create the gist.

Authorization

Token, user-name, and passd

When you need authorization, you can include :token, :user-name and :passd in github-client:github-api-call as keywords.

Here's how it works:

  • If you input :token, will use token you provided
  • If no :token given but client has token already, it will use token stored in client
  • If neither :token nor client's token is given, but has :passd keyword, will use :user-name & passd as authorization. (I just assume you give :user-name too, when you give :passd)

About

Common Lisp Github REST API Client

Topics

Resources

Stars

18 stars

Watchers

3 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Highlight search terms from Google/DuckDuckGo/Bing referrer (function() { var ref = document.referrer; var terms = []; if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) { var url = new URL(ref); var q = url.searchParams.get('q') || url.searchParams.get('p'); if (q) { terms = q.split(/\s+/).filter(function(t) { return t.length > 2; }); } } if (terms.length === 0) return; var style = document.createElement('style'); style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }'; document.head.appendChild(style); function highlight(node) { if (node.nodeType === 3) { // text node var text = node.textContent; var found = false; terms.forEach(function(term) { var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi'); if (regex.test(text)) { found = true; var frag = document.createDocumentFragment(); var parts = text.split(regex); parts.forEach(function(part, i) { if (i % 2 === 0) { frag.appendChild(document.createTextNode(part)); } else { var span = document.createElement('span'); span.className = 'userscript-highlight'; span.textContent = part; frag.appendChild(span); } }); node.parentNode.replaceChild(frag, node); } }); } else if (node.nodeType === 1 && node.childNodes) { // element var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT']; if (!skipTags.includes(node.tagName)) { Array.from(node.childNodes).forEach(highlight); } } } highlight(document.body); // Re-highlight on dynamic content var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1 || node.nodeType === 3) highlight(node); }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' GitHub - ccqpein/Github-API-CL: Common Lisp Github REST API Client · GitHub
Skip to content

Repository files navigation

README

This repo is a simple client for the GitHub Rest V3 API.

I didn't find a full API on one page, so I gathered it from many pages. You might have to put API details into a JSON file yourself. Check out api.json to see how.

You can find the documents here.

How to Use

Please refer to ./example

Dependencies

I use yason for json parser, dexador for http client.

Install

This repo has already been deployed to quicklisp. You can simply use (ql:quickload "github-api-cl") to install it.

Read api.json file

Suppose we have api.json looks like:

{
"repositories": {
"repositories": {
"List repositories for a user": {
"parameters": [
["type", "string"],
["sort","string"],
["direction","string"]
],
"api": "GET /users/:username/repos",
"link": "https://developer.github.com/v3/repos/#list-repositories-for-a-user"
}
}
}
}

Examples:

;; load system first
(ql:quickload "github-api-cl")
;; read api.json in this repo, path var is github-api-doc::*api-json-file-path*
(github-api-doc:read-api-json) ;; => return a hashtable of this json;; OR you can give path specially
(github-api-doc:read-api-json #P"/path/to/api.json")

Generate api instance

After read api.json file, you can generate api instance by using github-api-doc:make-api-doc-from-json

Examples:

;; read api.json
(defparameter*api-docs* (github-api-doc:read-api-json))
;; &rest arguments are the steps of reading json
(defparameter*api-doc* (github-api-doc:make-api-doc-from-json *api-docs*"repositories""repositories""List repositories for a user"))
;; Get api-doc: ;;api-doc object:;; api: GET /users/:username/repos,;; http method: GET,;; slots: (:username),;; fmt-control: (/users/~a/repos);; parameters: ((type string) (sort string) (direction string));; OR, you can make instance manually
(setf*api-doc* (make-instance'api-doc
:api"GET /users/:username/repos":parameters'(("type""string") ("sort""string") ("direction""string")))

The api.json file is very flexible as it's just a JSON file. You don't have to stick to the GitHub API structure if you don't want to. The only part that github-api-cl is concerned with is this section:

{
"parameters": [
["type", "string"],
["sort","string"],
["direction","string"]
],
"api": "GET /users/:username/repos",
}

You can read this json file and (github-api-doc:make-api-doc-from-json (github-api-doc:read-api-json #P"this-simple-api.json"))

Make github-api client

Making github-api client:

;; make instance of api-client
(defparameter*client-without-token* (make-instance'github-client:api-client))
;; if you have token for github rest api call, make like this
(defparameter*client-with-token* (make-instance'github-client:api-client :token"123"))

Call api

With client and api, now we can call api in our code:

;; call api with client and api we made before
(github-client:github-api-call *client-without-token**api-doc*)
;;; REPL will ask you to input `:username`, `type`, `sort`, and `direction`;;; Then, it will return the dex:http-response, you can find this MULTIPLE-VALUEs ;;; return format in https://github.com/fukamachi/dexador#following-redirects-get-or-head;; call POST method api with additional :content keyword
(github-client:github-api-call *client-without-token**api-doc*:headers'((header0 . value0) (header1 . value1))
:content"this argument pass to dexador directly")

github-api-call will call api with the default headers '(("Accept" . "application/vnd.github+json")). Any other headers pass to :headers will been added ("Accept" . "application/vnd.github+json").

From now, github-api-cl's job is done, left all http response back to you, you can do whatever you want.

Wait, if you do not want REPL ask you to input every slots and parameters:

(github-client:github-api-call *client-without-token**api-doc*:username"lisp":type"public":direction"test":neither-slots-nor-parameter1) ;; last keyword is redundant

With keywords input, REPL won't ask you anything, just call https://api.github.com/users/lisp/repos?type=\"public\"&direction=\"test\".

As example shows, :username fills api slot, :type & :direction are used for parameters. Meanwhile :neither-slots-nor-parameter doesn't play any role in this API.

For POST method api, :content is the keyword for add the content. It pass to :content keyword of dexador's POSTmethod. Check ./example/github-gist-cl to find how to create the gist.

Authorization

Token, user-name, and passd

When you need authorization, you can include :token, :user-name and :passd in github-client:github-api-call as keywords.

Here's how it works:

  • If you input :token, will use token you provided
  • If no :token given but client has token already, it will use token stored in client
  • If neither :token nor client's token is given, but has :passd keyword, will use :user-name & passd as authorization. (I just assume you give :user-name too, when you give :passd)

About

Common Lisp Github REST API Client

Topics

Resources

Stars

18 stars

Watchers

3 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Strip utm_, fbclid, gclid, etc. from all links on page (function() { var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content', 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid', 'ref', 'ref_src', 'source', 'medium', 'campaign']; function cleanUrl(url) { try { var u = new URL(url, window.location.origin); var changed = false; trackingParams.forEach(function(p) { if (u.searchParams.has(p)) { u.searchParams.delete(p); changed = true; } }); return changed ? u.toString() : url; } catch (e) { return url; } } function cleanLinks() { document.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } cleanLinks(); var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1) { if (node.tagName === 'A') cleanLinks(); node.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + ' GitHub - ccqpein/Github-API-CL: Common Lisp Github REST API Client · GitHub
Skip to content

Repository files navigation

README

This repo is a simple client for the GitHub Rest V3 API.

I didn't find a full API on one page, so I gathered it from many pages. You might have to put API details into a JSON file yourself. Check out api.json to see how.

You can find the documents here.

How to Use

Please refer to ./example

Dependencies

I use yason for json parser, dexador for http client.

Install

This repo has already been deployed to quicklisp. You can simply use (ql:quickload "github-api-cl") to install it.

Read api.json file

Suppose we have api.json looks like:

{
"repositories": {
"repositories": {
"List repositories for a user": {
"parameters": [
["type", "string"],
["sort","string"],
["direction","string"]
],
"api": "GET /users/:username/repos",
"link": "https://developer.github.com/v3/repos/#list-repositories-for-a-user"
}
}
}
}

Examples:

;; load system first
(ql:quickload "github-api-cl")
;; read api.json in this repo, path var is github-api-doc::*api-json-file-path*
(github-api-doc:read-api-json) ;; => return a hashtable of this json;; OR you can give path specially
(github-api-doc:read-api-json #P"/path/to/api.json")

Generate api instance

After read api.json file, you can generate api instance by using github-api-doc:make-api-doc-from-json

Examples:

;; read api.json
(defparameter*api-docs* (github-api-doc:read-api-json))
;; &rest arguments are the steps of reading json
(defparameter*api-doc* (github-api-doc:make-api-doc-from-json *api-docs*"repositories""repositories""List repositories for a user"))
;; Get api-doc: ;;api-doc object:;; api: GET /users/:username/repos,;; http method: GET,;; slots: (:username),;; fmt-control: (/users/~a/repos);; parameters: ((type string) (sort string) (direction string));; OR, you can make instance manually
(setf*api-doc* (make-instance'api-doc
:api"GET /users/:username/repos":parameters'(("type""string") ("sort""string") ("direction""string")))

The api.json file is very flexible as it's just a JSON file. You don't have to stick to the GitHub API structure if you don't want to. The only part that github-api-cl is concerned with is this section:

{
"parameters": [
["type", "string"],
["sort","string"],
["direction","string"]
],
"api": "GET /users/:username/repos",
}

You can read this json file and (github-api-doc:make-api-doc-from-json (github-api-doc:read-api-json #P"this-simple-api.json"))

Make github-api client

Making github-api client:

;; make instance of api-client
(defparameter*client-without-token* (make-instance'github-client:api-client))
;; if you have token for github rest api call, make like this
(defparameter*client-with-token* (make-instance'github-client:api-client :token"123"))

Call api

With client and api, now we can call api in our code:

;; call api with client and api we made before
(github-client:github-api-call *client-without-token**api-doc*)
;;; REPL will ask you to input `:username`, `type`, `sort`, and `direction`;;; Then, it will return the dex:http-response, you can find this MULTIPLE-VALUEs ;;; return format in https://github.com/fukamachi/dexador#following-redirects-get-or-head;; call POST method api with additional :content keyword
(github-client:github-api-call *client-without-token**api-doc*:headers'((header0 . value0) (header1 . value1))
:content"this argument pass to dexador directly")

github-api-call will call api with the default headers '(("Accept" . "application/vnd.github+json")). Any other headers pass to :headers will been added ("Accept" . "application/vnd.github+json").

From now, github-api-cl's job is done, left all http response back to you, you can do whatever you want.

Wait, if you do not want REPL ask you to input every slots and parameters:

(github-client:github-api-call *client-without-token**api-doc*:username"lisp":type"public":direction"test":neither-slots-nor-parameter1) ;; last keyword is redundant

With keywords input, REPL won't ask you anything, just call https://api.github.com/users/lisp/repos?type=\"public\"&direction=\"test\".

As example shows, :username fills api slot, :type & :direction are used for parameters. Meanwhile :neither-slots-nor-parameter doesn't play any role in this API.

For POST method api, :content is the keyword for add the content. It pass to :content keyword of dexador's POSTmethod. Check ./example/github-gist-cl to find how to create the gist.

Authorization

Token, user-name, and passd

When you need authorization, you can include :token, :user-name and :passd in github-client:github-api-call as keywords.

Here's how it works:

  • If you input :token, will use token you provided
  • If no :token given but client has token already, it will use token stored in client
  • If neither :token nor client's token is given, but has :passd keyword, will use :user-name & passd as authorization. (I just assume you give :user-name too, when you give :passd)

About

Common Lisp Github REST API Client

Topics

Resources

Stars

18 stars

Watchers

3 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Auto-enable theater mode on YouTube (function() { function tryTheater() { var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]'); if (btn && !btn.classList.contains('activated')) { btn.click(); } } // Try immediately tryTheater(); // Try after navigation (SPA) var lastUrl = location.href; setInterval(function() { if (location.href !== lastUrl) { lastUrl = location.href; setTimeout(tryTheater, 500); } }, 1000); // Also try on player load var observer = new MutationObserver(tryTheater); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' GitHub - ccqpein/Github-API-CL: Common Lisp Github REST API Client · GitHub
Skip to content

Repository files navigation

README

This repo is a simple client for the GitHub Rest V3 API.

I didn't find a full API on one page, so I gathered it from many pages. You might have to put API details into a JSON file yourself. Check out api.json to see how.

You can find the documents here.

How to Use

Please refer to ./example

Dependencies

I use yason for json parser, dexador for http client.

Install

This repo has already been deployed to quicklisp. You can simply use (ql:quickload "github-api-cl") to install it.

Read api.json file

Suppose we have api.json looks like:

{
"repositories": {
"repositories": {
"List repositories for a user": {
"parameters": [
["type", "string"],
["sort","string"],
["direction","string"]
],
"api": "GET /users/:username/repos",
"link": "https://developer.github.com/v3/repos/#list-repositories-for-a-user"
}
}
}
}

Examples:

;; load system first
(ql:quickload "github-api-cl")
;; read api.json in this repo, path var is github-api-doc::*api-json-file-path*
(github-api-doc:read-api-json) ;; => return a hashtable of this json;; OR you can give path specially
(github-api-doc:read-api-json #P"/path/to/api.json")

Generate api instance

After read api.json file, you can generate api instance by using github-api-doc:make-api-doc-from-json

Examples:

;; read api.json
(defparameter*api-docs* (github-api-doc:read-api-json))
;; &rest arguments are the steps of reading json
(defparameter*api-doc* (github-api-doc:make-api-doc-from-json *api-docs*"repositories""repositories""List repositories for a user"))
;; Get api-doc: ;;api-doc object:;; api: GET /users/:username/repos,;; http method: GET,;; slots: (:username),;; fmt-control: (/users/~a/repos);; parameters: ((type string) (sort string) (direction string));; OR, you can make instance manually
(setf*api-doc* (make-instance'api-doc
:api"GET /users/:username/repos":parameters'(("type""string") ("sort""string") ("direction""string")))

The api.json file is very flexible as it's just a JSON file. You don't have to stick to the GitHub API structure if you don't want to. The only part that github-api-cl is concerned with is this section:

{
"parameters": [
["type", "string"],
["sort","string"],
["direction","string"]
],
"api": "GET /users/:username/repos",
}

You can read this json file and (github-api-doc:make-api-doc-from-json (github-api-doc:read-api-json #P"this-simple-api.json"))

Make github-api client

Making github-api client:

;; make instance of api-client
(defparameter*client-without-token* (make-instance'github-client:api-client))
;; if you have token for github rest api call, make like this
(defparameter*client-with-token* (make-instance'github-client:api-client :token"123"))

Call api

With client and api, now we can call api in our code:

;; call api with client and api we made before
(github-client:github-api-call *client-without-token**api-doc*)
;;; REPL will ask you to input `:username`, `type`, `sort`, and `direction`;;; Then, it will return the dex:http-response, you can find this MULTIPLE-VALUEs ;;; return format in https://github.com/fukamachi/dexador#following-redirects-get-or-head;; call POST method api with additional :content keyword
(github-client:github-api-call *client-without-token**api-doc*:headers'((header0 . value0) (header1 . value1))
:content"this argument pass to dexador directly")

github-api-call will call api with the default headers '(("Accept" . "application/vnd.github+json")). Any other headers pass to :headers will been added ("Accept" . "application/vnd.github+json").

From now, github-api-cl's job is done, left all http response back to you, you can do whatever you want.

Wait, if you do not want REPL ask you to input every slots and parameters:

(github-client:github-api-call *client-without-token**api-doc*:username"lisp":type"public":direction"test":neither-slots-nor-parameter1) ;; last keyword is redundant

With keywords input, REPL won't ask you anything, just call https://api.github.com/users/lisp/repos?type=\"public\"&direction=\"test\".

As example shows, :username fills api slot, :type & :direction are used for parameters. Meanwhile :neither-slots-nor-parameter doesn't play any role in this API.

For POST method api, :content is the keyword for add the content. It pass to :content keyword of dexador's POSTmethod. Check ./example/github-gist-cl to find how to create the gist.

Authorization

Token, user-name, and passd

When you need authorization, you can include :token, :user-name and :passd in github-client:github-api-call as keywords.

Here's how it works:

  • If you input :token, will use token you provided
  • If no :token given but client has token already, it will use token stored in client
  • If neither :token nor client's token is given, but has :passd keyword, will use :user-name & passd as authorization. (I just assume you give :user-name too, when you give :passd)

About

Common Lisp Github REST API Client

Topics

Resources

Stars

18 stars

Watchers

3 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Remove or un-stick sticky/fixed headers that block content (function() { function unstick() { document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) { if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') { el.style.position = 'static'; el.style.top = 'auto'; el.style.zIndex = 'auto'; } }); } unstick(); var observer = new MutationObserver(unstick); observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] }); })(); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' GitHub - ccqpein/Github-API-CL: Common Lisp Github REST API Client · GitHub
Skip to content

Repository files navigation

README

This repo is a simple client for the GitHub Rest V3 API.

I didn't find a full API on one page, so I gathered it from many pages. You might have to put API details into a JSON file yourself. Check out api.json to see how.

You can find the documents here.

How to Use

Please refer to ./example

Dependencies

I use yason for json parser, dexador for http client.

Install

This repo has already been deployed to quicklisp. You can simply use (ql:quickload "github-api-cl") to install it.

Read api.json file

Suppose we have api.json looks like:

{
"repositories": {
"repositories": {
"List repositories for a user": {
"parameters": [
["type", "string"],
["sort","string"],
["direction","string"]
],
"api": "GET /users/:username/repos",
"link": "https://developer.github.com/v3/repos/#list-repositories-for-a-user"
}
}
}
}

Examples:

;; load system first
(ql:quickload "github-api-cl")
;; read api.json in this repo, path var is github-api-doc::*api-json-file-path*
(github-api-doc:read-api-json) ;; => return a hashtable of this json;; OR you can give path specially
(github-api-doc:read-api-json #P"/path/to/api.json")

Generate api instance

After read api.json file, you can generate api instance by using github-api-doc:make-api-doc-from-json

Examples:

;; read api.json
(defparameter*api-docs* (github-api-doc:read-api-json))
;; &rest arguments are the steps of reading json
(defparameter*api-doc* (github-api-doc:make-api-doc-from-json *api-docs*"repositories""repositories""List repositories for a user"))
;; Get api-doc: ;;api-doc object:;; api: GET /users/:username/repos,;; http method: GET,;; slots: (:username),;; fmt-control: (/users/~a/repos);; parameters: ((type string) (sort string) (direction string));; OR, you can make instance manually
(setf*api-doc* (make-instance'api-doc
:api"GET /users/:username/repos":parameters'(("type""string") ("sort""string") ("direction""string")))

The api.json file is very flexible as it's just a JSON file. You don't have to stick to the GitHub API structure if you don't want to. The only part that github-api-cl is concerned with is this section:

{
"parameters": [
["type", "string"],
["sort","string"],
["direction","string"]
],
"api": "GET /users/:username/repos",
}

You can read this json file and (github-api-doc:make-api-doc-from-json (github-api-doc:read-api-json #P"this-simple-api.json"))

Make github-api client

Making github-api client:

;; make instance of api-client
(defparameter*client-without-token* (make-instance'github-client:api-client))
;; if you have token for github rest api call, make like this
(defparameter*client-with-token* (make-instance'github-client:api-client :token"123"))

Call api

With client and api, now we can call api in our code:

;; call api with client and api we made before
(github-client:github-api-call *client-without-token**api-doc*)
;;; REPL will ask you to input `:username`, `type`, `sort`, and `direction`;;; Then, it will return the dex:http-response, you can find this MULTIPLE-VALUEs ;;; return format in https://github.com/fukamachi/dexador#following-redirects-get-or-head;; call POST method api with additional :content keyword
(github-client:github-api-call *client-without-token**api-doc*:headers'((header0 . value0) (header1 . value1))
:content"this argument pass to dexador directly")

github-api-call will call api with the default headers '(("Accept" . "application/vnd.github+json")). Any other headers pass to :headers will been added ("Accept" . "application/vnd.github+json").

From now, github-api-cl's job is done, left all http response back to you, you can do whatever you want.

Wait, if you do not want REPL ask you to input every slots and parameters:

(github-client:github-api-call *client-without-token**api-doc*:username"lisp":type"public":direction"test":neither-slots-nor-parameter1) ;; last keyword is redundant

With keywords input, REPL won't ask you anything, just call https://api.github.com/users/lisp/repos?type=\"public\"&direction=\"test\".

As example shows, :username fills api slot, :type & :direction are used for parameters. Meanwhile :neither-slots-nor-parameter doesn't play any role in this API.

For POST method api, :content is the keyword for add the content. It pass to :content keyword of dexador's POSTmethod. Check ./example/github-gist-cl to find how to create the gist.

Authorization

Token, user-name, and passd

When you need authorization, you can include :token, :user-name and :passd in github-client:github-api-call as keywords.

Here's how it works:

  • If you input :token, will use token you provided
  • If no :token given but client has token already, it will use token stored in client
  • If neither :token nor client's token is given, but has :passd keyword, will use :user-name & passd as authorization. (I just assume you give :user-name too, when you give :passd)

About

Common Lisp Github REST API Client

Topics

Resources

Stars

18 stars

Watchers

3 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Universal Dark Mode - works on any site (function() { var enabled = true; function applyDarkMode() { if (!enabled) return; // Create style element if it doesn't exist var style = document.getElementById('universal-dark-mode-style'); if (!style) { style = document.createElement('style'); style.id = 'universal-dark-mode-style'; document.head.appendChild(style); } // Dark mode CSS - inverts colors but preserves images/video style.textContent = ' /* Invert everything except media */ html { filter: invert(1) hue-rotate(180deg) !important; background: #1a1a2e !important; } /* Restore images, videos, iframes, canvas */ img, video, iframe, canvas, svg, picture, [style*="background-image"] { filter: invert(1) hue-rotate(180deg) !important; } /* Preserve specific elements that should not be inverted */ .no-dark-mode, .no-dark-mode *, [data-theme="light"], [data-theme="light"], .ace_editor, .ace_editor *, .CodeMirror, .CodeMirror *, .monaco-editor, .monaco-editor *, .markdown-body pre, .markdown-body pre *, .highlight, .highlight *, pre code, pre code * { filter: none !important; } /* Fix common UI elements */ .modal, .popup, .dropdown-menu, .tooltip, .popover { filter: invert(1) hue-rotate(180deg) !important; background: #2d2d44 !important; border-color: #444 !important; } /* Scrollbars */ ::-webkit-scrollbar { background: #1a1a2e !important; } ::-webkit-scrollbar-thumb { background: #444 !important; } ::-webkit-scrollbar-thumb:hover { background: #555 !important; } /* Selection */ ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; } ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; } '; } function removeDarkMode() { var style = document.getElementById('universal-dark-mode-style'); if (style) style.remove(); } // Toggle with Alt+Shift+D document.addEventListener('keydown', function(e) { if (e.altKey && e.shiftKey && e.key === 'D') { e.preventDefault(); enabled = !enabled; if (enabled) { applyDarkMode(); console.log('[Universal Dark Mode] Enabled'); } else { removeDarkMode(); console.log('[Universal Dark Mode] Disabled'); } } }); // Apply on load applyDarkMode(); // Re-apply on dynamic content var observer = new MutationObserver(function(mutations) { if (enabled && !document.getElementById('universal-dark-mode-style')) { applyDarkMode(); } }); observer.observe(document.head, { childList: true }); console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle'); })(); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })(); GitHub - ccqpein/Github-API-CL: Common Lisp Github REST API Client · GitHub
Skip to content

Repository files navigation

README

This repo is a simple client for the GitHub Rest V3 API.

I didn't find a full API on one page, so I gathered it from many pages. You might have to put API details into a JSON file yourself. Check out api.json to see how.

You can find the documents here.

How to Use

Please refer to ./example

Dependencies

I use yason for json parser, dexador for http client.

Install

This repo has already been deployed to quicklisp. You can simply use (ql:quickload "github-api-cl") to install it.

Read api.json file

Suppose we have api.json looks like:

{
"repositories": {
"repositories": {
"List repositories for a user": {
"parameters": [
["type", "string"],
["sort","string"],
["direction","string"]
],
"api": "GET /users/:username/repos",
"link": "https://developer.github.com/v3/repos/#list-repositories-for-a-user"
}
}
}
}

Examples:

;; load system first
(ql:quickload "github-api-cl")
;; read api.json in this repo, path var is github-api-doc::*api-json-file-path*
(github-api-doc:read-api-json) ;; => return a hashtable of this json;; OR you can give path specially
(github-api-doc:read-api-json #P"/path/to/api.json")

Generate api instance

After read api.json file, you can generate api instance by using github-api-doc:make-api-doc-from-json

Examples:

;; read api.json
(defparameter*api-docs* (github-api-doc:read-api-json))
;; &rest arguments are the steps of reading json
(defparameter*api-doc* (github-api-doc:make-api-doc-from-json *api-docs*"repositories""repositories""List repositories for a user"))
;; Get api-doc: ;;api-doc object:;; api: GET /users/:username/repos,;; http method: GET,;; slots: (:username),;; fmt-control: (/users/~a/repos);; parameters: ((type string) (sort string) (direction string));; OR, you can make instance manually
(setf*api-doc* (make-instance'api-doc
:api"GET /users/:username/repos":parameters'(("type""string") ("sort""string") ("direction""string")))

The api.json file is very flexible as it's just a JSON file. You don't have to stick to the GitHub API structure if you don't want to. The only part that github-api-cl is concerned with is this section:

{
"parameters": [
["type", "string"],
["sort","string"],
["direction","string"]
],
"api": "GET /users/:username/repos",
}

You can read this json file and (github-api-doc:make-api-doc-from-json (github-api-doc:read-api-json #P"this-simple-api.json"))

Make github-api client

Making github-api client:

;; make instance of api-client
(defparameter*client-without-token* (make-instance'github-client:api-client))
;; if you have token for github rest api call, make like this
(defparameter*client-with-token* (make-instance'github-client:api-client :token"123"))

Call api

With client and api, now we can call api in our code:

;; call api with client and api we made before
(github-client:github-api-call *client-without-token**api-doc*)
;;; REPL will ask you to input `:username`, `type`, `sort`, and `direction`;;; Then, it will return the dex:http-response, you can find this MULTIPLE-VALUEs ;;; return format in https://github.com/fukamachi/dexador#following-redirects-get-or-head;; call POST method api with additional :content keyword
(github-client:github-api-call *client-without-token**api-doc*:headers'((header0 . value0) (header1 . value1))
:content"this argument pass to dexador directly")

github-api-call will call api with the default headers '(("Accept" . "application/vnd.github+json")). Any other headers pass to :headers will been added ("Accept" . "application/vnd.github+json").

From now, github-api-cl's job is done, left all http response back to you, you can do whatever you want.

Wait, if you do not want REPL ask you to input every slots and parameters:

(github-client:github-api-call *client-without-token**api-doc*:username"lisp":type"public":direction"test":neither-slots-nor-parameter1) ;; last keyword is redundant

With keywords input, REPL won't ask you anything, just call https://api.github.com/users/lisp/repos?type=\"public\"&direction=\"test\".

As example shows, :username fills api slot, :type & :direction are used for parameters. Meanwhile :neither-slots-nor-parameter doesn't play any role in this API.

For POST method api, :content is the keyword for add the content. It pass to :content keyword of dexador's POSTmethod. Check ./example/github-gist-cl to find how to create the gist.

Authorization

Token, user-name, and passd

When you need authorization, you can include :token, :user-name and :passd in github-client:github-api-call as keywords.

Here's how it works:

  • If you input :token, will use token you provided
  • If no :token given but client has token already, it will use token stored in client
  • If neither :token nor client's token is given, but has :passd keyword, will use :user-name & passd as authorization. (I just assume you give :user-name too, when you give :passd)

About

Common Lisp Github REST API Client

Topics

Resources

Stars

18 stars

Watchers

3 watching

Forks

Releases

Packages

Contributors

Languages