idk @Sheyan I haven’t touched them in a while. We were waiting for an implementation that was going to bypass Rustler. I don’t know what the state of that work is. I haven’t followed up on it.

Rustler Precompiled was recently released. I plan to built it into pact_elixir in the coming weeks.

Is there official support for Elixir yet?

hey folks! is there any plans of supporting elixir?

Unfortunately the history of this channel is lost to the depths of the free tier. There are no official plans, albeit there have been starts

you can see some of that history here: https://docs.pact.io/slack/pact-elixir.html

We (maintainers) are of course happy to support a community initiative to bring one up to speed

thanks @Matt (pactflow.io / pact-js / pact-go)

Should we rename this to pact-beam and include discussions of the new pact_erlang library as well?

Makes sense to me. This channel has been pretty quiet since I joined it long ago. I think discussing any beam-related stuff here makes sense.

We can rename if needed. We are working to get a paid workspace, hopefully that will be soon, and then the elixir history will be back

I’d expect (in time) that both Elixir and Erlang would have separate DSLs, specific to each language. Despite the common runtime, they are separate. I say that without knowing much. Is “beam” the common platform that would be obvious to both languages / the ecosystem to join?

The inaccurate but quickest approximation I can give is like the JVM for Java, Scala, Clojure, etc.

that’s what I was thinking

so

#pact-beam

would cover both Erlang and Elixir?

So we can share/reuse stuff across the board if we choose. But yes you do end up with language-specific DSLs for stuff.

Yeah it'd cover those among some others

has renamed the channel from "pact-elixir" to "pact-beam"

@Priyaranjan Mudliar - where did you land with the Erlang bindings? (and welcome blobwave )

set the channel description: Discuss Elixir and Erlang related Pact implementations. Work in progress for Elixir exists at https://github.com/elitau/pact_elixir

The erlang wip is at https://github.com/greyorange-labs/pact-erlang With the package at https://hex.pm/packages/pact_erlang

set the channel description: Discuss Elixir and Erlang related Pact implementations. Work in progress for Elixir exists at https://github.com/elitau/pact_elixir The erlang wip is at https://github.com/greyorange-labs/pact-erlang (https://hex.pm/packages/pact_erlang)

Request for comments: DSL and project structure for pact-erlang: https://github.com/greyorange-labs/pact-erlang/issues/11

pact_erlang version 0.2.0 released with the new map-based DSL: https://github.com/greyorange-labs/pact_erlang Sample usage:

PactRef = pact:v4(<<"myapp">>, <<"animal_service">>),
AnimalObject = #{<<"name">> => <<"Mary">>, <<"type">> => <<"alligator">>},
{ok, Port} = pact:interaction(PactRef,
#{
    given => <<"an alligator with the name Mary exists">>,
    upon_receiving => <<"a request to GET an animal: Mary">>,
    with_request => #{
        method => <<"GET">>,
        path => <<"/animals/Mary">>
    },
    will_respond_with => #{
        status => 200,
        headers => #{
            <<"Content-Type">> => <<"application/json">>
        },
        body => thoas:encode(AnimalObject)
    }
}),
?assertMatch({ok, AnimalObject}, animal_service_interface:get_animal(Port, "Mary")),
{ok, matched} = pact:verify(PactRef),
pact:write(PactRef, <<"./pacts">>),
pact:cleanup(PactRef).