All Projects → wojtekmach → Github_ecto

wojtekmach / Github_ecto

Ecto adapter for GitHub API

Programming Languages

elixir
2628 projects

Projects that are alternatives of or similar to Github ecto

Filterable
Filtering from incoming params in Elixir/Ecto/Phoenix with easy to use DSL.
Stars: ✭ 83 (-27.19%)
Mutual labels:  ecto
Opensource
Conheça os projetos Open Source na Globo.com
Stars: ✭ 100 (-12.28%)
Mutual labels:  github-api
Kronky
Kronky bridges the gap between Ecto and Absinthe GraphQL by listing validation messages in a mutation payload.
Stars: ✭ 112 (-1.75%)
Mutual labels:  ecto
Github Clone
⬇️ ⠀git clone repo subdirectories
Stars: ✭ 87 (-23.68%)
Mutual labels:  github-api
Ecto state machine
State machine pattern for Ecto
Stars: ✭ 91 (-20.18%)
Mutual labels:  ecto
Lastversion
Find the latest release version of an arbitrary project
Stars: ✭ 103 (-9.65%)
Mutual labels:  github-api
Gitmad
Monitor, Alert, and Discover sensitive info and data leakage on Github.
Stars: ✭ 81 (-28.95%)
Mutual labels:  github-api
Scrivener html
HTML view helpers for Scrivener
Stars: ✭ 112 (-1.75%)
Mutual labels:  ecto
Defql
Create elixir functions with SQL as a body.
Stars: ✭ 100 (-12.28%)
Mutual labels:  ecto
Rxgithub
An example of MVVM using RxSwift and Swinject (DI)
Stars: ✭ 109 (-4.39%)
Mutual labels:  github-api
Github Rest Apis For Insomnia
💯 A complete set of GitHub REST API route specifications that can be imported straight into Insomnia REST Client
Stars: ✭ 90 (-21.05%)
Mutual labels:  github-api
Dart hub
A GitHub client written in Flutter.
Stars: ✭ 91 (-20.18%)
Mutual labels:  github-api
Llum
Llum (light in catalan language) illuminates your Laravel projects speeding up your Github/Laravel development workflow
Stars: ✭ 107 (-6.14%)
Mutual labels:  github-api
Repopeek
RepoPeek is a python script to get details about a repository without cloning it.
Stars: ✭ 85 (-25.44%)
Mutual labels:  github-api
Elixir Cowboy React Spa
Example application that shows how to use Cowboy 2.0 in conjunction with React and Redux to create data driven Single Page Applications
Stars: ✭ 112 (-1.75%)
Mutual labels:  ecto
Keynuker
🔐💥 KeyNuker - nuke AWS keys accidentally leaked to Github
Stars: ✭ 82 (-28.07%)
Mutual labels:  github-api
Vblog
使用GitHub API 搭建一个可动态发布文章的博客
Stars: ✭ 1,375 (+1106.14%)
Mutual labels:  github-api
Gitstats
An open source github contribution analyzer
Stars: ✭ 115 (+0.88%)
Mutual labels:  github-api
Rethinkdb ecto
RethinkDB adapter for Ecto.
Stars: ✭ 112 (-1.75%)
Mutual labels:  ecto
Year On Github
🐙 Share your Github stats for 2020 on Twitter
Stars: ✭ 108 (-5.26%)
Mutual labels:  github-api

GitHub.Ecto

Build Status

Example

# Paste below to iex

# 0. Install this application (see instructions at the end of the README)

# 1. Define `Repo` (or `GitHub` or whatever):
defmodule Repo do
  use Ecto.Repo,
    otp_app: :my_app,
    adapter: GitHub.Ecto
end

# 2. Configure this application. In a real project you'd configure it in config/*.exs as does every other adapter.
Application.put_env(:my_app, Repo, [
  token: nil # set to a string to be able to write or access private repos. Be careful!
])

# 3. Start the Repo process. In a real project you'd put the Repo module in your project's supervision tree:
{:ok, _pid} = Repo.start_link

# 4. Import Ecto.Query
import Ecto.Query

# 5. List titles and comment counts of all open feature requests in Ecto, sorted by comment counts:
q = from(i in GitHub.Issue, # or: from i in "issues" for all fields that API returns
         select: {i.title, i.comments},
         where: i.repo == "elixir-ecto/ecto" and
                i.state == "open" and
                "Kind:Feature" in i.labels,
         order_by: [desc: :comments])
Repo.all(q)
# => [{"Introducing Ecto.Multi", 60},
#     {"Support map update syntax", 14},
#     {"Create test db from development schema", 9},
#     {"Provide integration tests with ownership with Hound", 0}]
# (as of 2015-02-14)

# 6. (optional) Create an issue if something doesn't look right :-)
issue = Repo.insert!(%GitHub.Issue{title: "Something went wrong", body: "Everything's broken", repo: "wojtekmach/github_ecto"})

# 7. (optional) Mark the issue as resolved.
Repo.update!(GitHub.Issue.changeset(issue, %{state: "closed"}))

See more examples of usage in tests. Also see the Ecto API and GitHub API.

Why?

First of all this library is in a very early stage and isn't suitable for production use. Second of all, it may never be suitable for production use :-) There're already existing wrappers for GitHub API and, honestly, it may or may not be such a good idea to wrap it with Ecto. The primary goal of this project is for me to learn more about Ecto and it's internals and secondarily to build something useful :-)

Installation

  1. Add github_ecto to your list of dependencies in mix.exs:
```elixir
def deps do
  [{:github_ecto, github: "wojtekmach/github_ecto"}]
end
```
  1. Ensure github_ecto is started before your application:
```elixir
def application do
  [applications: [:logger, :github_ecto, :ecto]]
end
```

License

The MIT License (MIT)

Copyright (c) 2016 Wojciech Mach

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].