-
Updated
Dec 23, 2020 - Elixir
Elixir
Elixir leverages the Erlang VM, known for running low-latency, distributed and fault-tolerant systems, while also being successfully used in web development, and the embedded software domain.
Here are 6,506 public repositories matching this topic...
-
Updated
Dec 22, 2020 - Python
-
Updated
Dec 4, 2020
-
Updated
Dec 23, 2020 - Elixir
-
Updated
Dec 19, 2020 - Elixir
-
Updated
Dec 22, 2020 - Elixir
-
Updated
Dec 13, 2020 - Elixir
-
Updated
Dec 21, 2020 - SCSS
-
Updated
Oct 6, 2020 - Elixir
Problem
We need to be able to calculate how long it takes for a conversation to be closed ("resolved").
Right now the way we determine if a conversation is closed is by looking at the status field, which can currently only be "open" or "closed".
Solution
- Set up a database migration to add the
closed_atfield to theconversationstable (as autc_datetime) - Update the
-
Updated
Dec 22, 2020 - Elixir
-
Updated
Dec 22, 2020 - Elixir
-
Updated
Feb 21, 2020 - Elixir
-
Updated
Dec 23, 2020 - Elixir
-
Updated
Dec 23, 2020 - Elixir
Below is a list of all the known Erlang standard library functions found in Elixir's Standard Library that have not been implemented in some way yet in ElixirScript. Implementations should go here
For anyone looking to implement a function the steps would be to:
- Pick a function or functions from
Fix Lints
-
Updated
Dec 11, 2020 - Elixir
-
Updated
Dec 21, 2020 - Elixir
-
Updated
Dec 20, 2020 - Java
Finch adapter
A tiny adapter for https://github.com/keathley/finch - a HTTP client with built-in pooling.
Instead of building own mint+pooling adapter we could nicely integrate with Finch.
Something like this:
defmodule Tesla.Adapter.Finch do
@behaviour Tesla.Adapter
def call(env, opts) do
opts = Tesla.Adapter.opts(env, opts)
case Finch.request(name, env.method, env.url,Created by José Valim
Released September 8, 2014
- Organization
- elixir-lang
- Website
- elixir-lang.org
- Wikipedia
- Wikipedia
Steps to reproduce
Run
asdf. In help output a line is printed for theasdf envcommand:I would assume
<command>is an arbitrary command. But from what I can tell needs to be a plugin name or a shim name? I'm also not sure how this differs from executing the shim directly.FY