Instead of producing `{{Module}}.Auto` module, append encoder/decoders inside `{{Module}}` file itself #4

choonkeat · 2021-04-25T06:21:30Z

Upside 👍 we don't force the hand of the developers to expose the innards of the types

module Example exposing (Opaque)

type Opaque = Opaque String Int

... more code

-- SPECIAL COMMENT
-- EVERYTHING BELOW IS AUTO GENERATED

autoDecodeOpaque : Json.Decode.Decoder Opaque
autoDecodeOpaque = ... more code

autoEncodeOpaque : Opaque -> Json.Encode.Value
autoEncodeOpaque a = ... more code

Downside 👎 developers will have unignorable diff in their code commits
(instead of inlining, standard encoder decoders should be published as elm package for import to reduce the noise here)

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Instead of producing `{{Module}}.Auto` module, append encoder/decoders inside `{{Module}}` file itself #4

Instead of producing `{{Module}}.Auto` module, append encoder/decoders inside `{{Module}}` file itself #4

choonkeat commented Apr 25, 2021 •

edited

Loading

Instead of producing {{Module}}.Auto module, append encoder/decoders inside {{Module}} file itself #4

Instead of producing {{Module}}.Auto module, append encoder/decoders inside {{Module}} file itself #4

Comments

choonkeat commented Apr 25, 2021 • edited Loading

Instead of producing `{{Module}}.Auto` module, append encoder/decoders inside `{{Module}}` file itself #4

Instead of producing `{{Module}}.Auto` module, append encoder/decoders inside `{{Module}}` file itself #4

choonkeat commented Apr 25, 2021 •

edited

Loading