profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/maartenvanvliet/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Maarten van Vliet maartenvanvliet Rotterdam, the Netherlands https://www.maartenvanvliet.nl

howtographql/howtographql 7658

The Fullstack Tutorial for GraphQL

beam-community/awesome-phoenix-liveview 96

A curated list of awesome Phoenix LiveView repositories, blog posts or other resources

maartenvanvliet/apq 36

Support for Automatic Persisted Queries in Absinthe

maartenvanvliet/absinthe_trace_reporter 13

Apollo Engine reporter that sends Absinthe traces built by https://github.com/sikanhe/apollo-tracing-elixir to Apollo engine directly without having to use the (deprecated) engine proxy.

maartenvanvliet/absinthe_sdl 7

Convert Absinthe Schemas to SDL syntax

maartenvanvliet/apq_example 2

Example app for https://github.com/maartenvanvliet/apq

maartenvanvliet/artem 2

Library to aid in Absinthe graphql testing

maartenvanvliet/artem_introspection_schema 1

Artem Introspection Schema is a library to build Absinthe schema's from introspection query results

maartenvanvliet/blefescu 1

Simple image resizing web server in go

Pull request review commentelixir-ecto/ecto

Add Ecto.Enum.mappings/2

 defmodule Ecto.EnumTest do                   %{                     on_dump: %{bar: "baar", baz: "baaz", foo: "fooo"},                     on_load: %{"baar" => :bar, "baaz" => :baz, "fooo" => :foo},-                    values: [:foo, :bar, :baz],+                    mappings: [foo: "fooo", bar: "baar", baz: "baaz"],

My reason to chose a keyword list over a map is the fact that the user inputs a keyword list when creating a Ecto.Enum field, so it seemed consistent returning the exact same thing the user inputted. Yet, as you pointed out, this didn't reflect the exact mappings that are done on on_dump and on_load (these are maps, and the last one would take precedence). I opened another PR that prevents the user from inputting keyword lists with duplicate keys.

v0idpwn

comment created time in 42 minutes

PR opened elixir-ecto/ecto

Raise on duplicate values in Ecto.Enum

Duplicate values make so that only the last of the duplicates is taken into account, due to the fact that the keyword list is cast into a map for the on_load and on_dump values. With this commit we can avoid this scenario in compile time.

Pointed out by @wojtekmach on #3676

+55 -0

0 comment

2 changed files

pr created time in an hour

delete branch elixir-ecto/db_connection

delete branch : josevalim-patch-1

delete time in 5 hours

pull request commentelixir-ecto/db_connection

Update spec

:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:

josevalim

comment created time in 5 hours

push eventelixir-ecto/db_connection

José Valim

commit sha 6850853977a08ca9bbc7fc5d9d2b07f028720a6c

Update spec (#242) Closes #241

view details

push time in 5 hours

PR merged elixir-ecto/db_connection

Update spec

Closes #241

+4 -2

0 comment

1 changed file

josevalim

pr closed time in 5 hours

issue closedelixir-ecto/db_connection

Typespec Inconsistency

The return value here is a 5 element tuple, rather than the 4 element tuple declared in the typespec:

The typespec:

https://github.com/elixir-ecto/db_connection/blob/4d7e789943f1c3a0b54b871f3807a04303e666dc/lib/db_connection/holder.ex#L50

The offenders:

https://github.com/elixir-ecto/db_connection/blob/4d7e789943f1c3a0b54b871f3807a04303e666dc/lib/db_connection/holder.ex#L57

https://github.com/elixir-ecto/db_connection/blob/4d7e789943f1c3a0b54b871f3807a04303e666dc/lib/db_connection/holder.ex#L77

closed time in 5 hours

isaacsanders

PR opened elixir-ecto/db_connection

Update spec

Closes #241

+4 -2

0 comment

1 changed file

pr created time in 5 hours

create barnchelixir-ecto/db_connection

branch : josevalim-patch-1

created branch time in 5 hours

issue openedelixir-ecto/db_connection

Typespec Inconsistency

The return value here is a 5 element tuple, rather than the 4 element tuple declared in the typespec:

https://github.com/elixir-ecto/db_connection/blob/master/lib/db_connection/holder.ex#L57

created time in 5 hours

PR opened surface-ui/surface

Add a bug template

Adds a template for capturing bug reports from user's of Surface.

+16 -0

0 comment

1 changed file

pr created time in 6 hours

issue openedsurface-ui/surface

Bug: Unexpected error when using {... } sytnax on a slot

When attempting to use {... } syntax on a slot, you get an unexpected error message at the usage of the slot's component.

How to reproduce

<#slot {...Map.get(@something, :val)} />

Error

** (CaseClauseError) no case clause matching: {{:default, 0, %{}, %{state: ...omitted...}}}
        (scout 0.1.0) lib/myapp/live/show.sface:1: omitted
        (scout 0.1.0) lib/myapp/live/components/workflow.ex:25: omitted
        (phoenix_live_view 0.15.7) lib/phoenix_live_view/diff.ex:356: Phoenix.LiveView.Diff.traverse/6
        (phoenix_live_view 0.15.7) lib/phoenix_live_view/diff.ex:430: anonymous fn/4 in Phoenix.LiveView.Diff.traverse_dynamic/6
        (elixir 1.12.0) lib/enum.ex:2356: Enum."-reduce/3-lists^foldl/2-0-"/3
        (phoenix_live_view 0.15.7) lib/phoenix_live_view/diff.ex:356: Phoenix.LiveView.Diff.traverse/6

Expected behavior

A compile-time error should be raised that it is invalid to use {... }, :attrs and :props on a slot. Instead, the :args directive should be used.

created time in 6 hours

MemberEvent

issue openedsurface-ui/surface

HTML comment turns into span in stateful LiveComponent with multiple root elements

When a stateful live component has multiple root elements and one of those elements is a HTML comment then this comment is turned into a span.

In my case:

<!-- my comment -->

Turns into:

<span data-phx-component="6"> my comment </span>

created time in 6 hours

issue commenthowtographql/howtographql

Can't scroll in Safari

Just encountered this issue as well.

Safari 14.0.3 MacOS 11.2.3

vwkd

comment created time in 8 hours

startedGenymobile/scrcpy

started time in 10 hours

issue closedelixir-lang/elixir

Error Message Lies

Environment

  • Elixir & Erlang/OTP versions (elixir --version):
Erlang/OTP 24 [erts-12.0.2] [source] [64-bit] [smp:16:16] [ds:16:16:10] [async-threads:1] [jit]

Elixir 1.12.1 (compiled with Erlang/OTP 22)
  • Operating system: macOS Big Sur 11.2.3

Current behavior

iex(1)> String.to_existing_atom("valid_utf8")
** (ArgumentError) errors were found at the given arguments:

  * 1st argument: invalid UTF8 encoding

    :erlang.binary_to_existing_atom("valid_utf8", :utf8)

The error is a lie. It's valid UTF-8, it just doesn't exist as an atom.

Expected behavior

It would be great if it could tell us the atom doesn't exist. If that's not possible though, we should at least stop giving an incorrect reason.

closed time in 10 hours

JEG2

issue commentelixir-lang/elixir

Error Message Lies

Precisely, thanks @thiamsantos and @JEG2!

JEG2

comment created time in 10 hours

issue commentelixir-lang/elixir

Error Message Lies

I think it is the same error reported at https://github.com/elixir-lang/elixir/issues/11014. It seems to be already fixed in OTP https://github.com/erlang/otp/commit/c1942e39d44d50bb4bdf8e22456f31ee23931fdb.

JEG2

comment created time in 10 hours

issue openedelixir-lang/elixir

Error Message Lies

Environment

  • Elixir & Erlang/OTP versions (elixir --version):
Erlang/OTP 24 [erts-12.0.2] [source] [64-bit] [smp:16:16] [ds:16:16:10] [async-threads:1] [jit]

Elixir 1.12.1 (compiled with Erlang/OTP 22)
  • Operating system: macOS Big Sur 11.2.3

Current behavior

iex(1)> String.to_existing_atom("valid_utf8")
** (ArgumentError) errors were found at the given arguments:

  * 1st argument: invalid UTF8 encoding

    :erlang.binary_to_existing_atom("valid_utf8", :utf8)

The error is a lie. It's valid UTF-8, it just doesn't exist as an atom.

Expected behavior

It would be great if it could tell us the atom doesn't exist. If that's not possible though, we should at least stop giving an incorrect reason.

created time in 10 hours

pull request commentelixir-ecto/postgrex

correct formatting

:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:

bryanhuntesl

comment created time in 11 hours

push eventelixir-ecto/postgrex

bryanhuntesl

commit sha fc129a9597e79ab7cb413c1d58615b85e81eb076

fix formatting (#553)

view details

push time in 11 hours

PR merged elixir-ecto/postgrex

correct formatting
+3 -3

0 comment

1 changed file

bryanhuntesl

pr closed time in 11 hours

push eventaws-beam/aws-elixir

Philip Sampaio

commit sha 7a134e6910bba69372f9391a996b7c06e4cd9f34

Fix "restore-key" for cache - CI config We shouldn't restore cache from different OTP/Elixir versions.

view details

push time in 11 hours

PR opened elixir-ecto/postgrex

correct formatting
+3 -3

0 comment

1 changed file

pr created time in 11 hours

starteddnaeon/go-vcr

started time in 11 hours

issue openedabsinthe-graphql/absinthe

`mix clean` is sometimes required to see changes take effect

Environment

  • Elixir version (elixir -v): Erlang/OTP 23 [erts-11.2] [source] [64-bit] [smp:12:12] [ds:12:12:10] [async-threads:1] [hipe]
  • Absinthe version (mix deps | grep absinthe): absinthe 1.6.4 / absinthe_plug 1.5.8
  • Client Framework and version (Relay, Apollo, etc): graphiql

Expected behavior

Changing my types file from field(:id, :id) to field :id, :string do resolve(fn object, _, _ -> {:ok, GlobalId.encode(Spiff.Comment, object.id)} end) end

Sometimes does not register as a change

Actual behavior

id continued to behave as a plain db column until I ran mix clean and restarted. Then it works as expected. Restarting iex on its own is not enough to break the stale cache.

created time in 11 hours

push eventaws-beam/aws-elixir

Philip Sampaio

commit sha 8775313ede1dacf0034fdf53d6779c0751440a54

Update dependencies Also remove Eex from extra applications. We don't use this app.

view details

push time in 11 hours

startedoryon-osint/querytool

started time in 11 hours