RJ Dellecese
RJ Dellecese
If the Elm community's experience is anything to go by, decoders can be quite difficult for people to understand! Elixir and Erlang examples in the form of complete applications would...
```elm > import List.Extra as List > List.groupsOfVarying [0, 1] ["a"] [[],["a"]] : List (List String) > List.groupsOfVarying [1, 0] ["a"] [["a"]] : List (List String) ``` I would expect...
I tried to install a package on a new project and got this error: ``` -- INVALID ELM.JSON ------------------------------------------------------------ A valid package name look like "author/project" ``` The `"name"` in...
Have a single error type for decoding and a single error type for encoding, and turn `jsone` decoding/encoding errors into useful variants of those types.
Type holes (https://gcanti.github.io/fp-ts/modules/function.ts.html#hole) are useful for developing, but should basically never exist in production code. A `no-holes` or `no-type-holes` rule could help ensure that doesn't happen by accident!
# The problem Let's say that I have the following code: ```elm dropShadow : Element.Attribute msg dropShadow = Element.Border.shadow { offset = ( 0, 10 ) , size = 0...
Recent refactors have narrowed the usage of `ExtractDocument`, such that it is now only used in one place (`DataModelFromSchemaDefinition`). This PR specializes its implementation and updates some comments accordingly. (I...