NOTE: the latest version is 1.1.1

Renamed to anmolitor/elm-protoc-utils. It is published under that name, and new versions come out there.

Versions published as andreasewering/elm-protoc-utils still install under that name. 3 versions of 3 come from the new location (see their notes).

Rerouted (renamed, needs approval). The GitHub user or repository was renamed. The tag is still there, at the new name. The Lamdera package server serves a copy recovered from https://github.com/anmolitor/elm-protoc-utils.

What we checked: The repo moved to github.com/anmolitor/elm-protoc-utils and tag 1.1.0 is there; its commit b0071c1d1bd9 is from 2024-02-18 17:26 UTC, after the version was published (2023-12-17 18:39 UTC); elm.json differs from package.elm-lang.org's; the exposed modules match docs.json; the zip's SHA-1 is not the published one and nothing else confirms its contents.

We could not verify this copy against what was published, so the Lamdera compiler asks before using it (y/n). Without a terminal, as in CI, it stops with an error unless approved:

lamdera make --auto-approve-package-rerouting approves rerouted versions for that run,
LAMDERA_AUTO_APPROVE_PACKAGE_REROUTING=1 does the same for every run in that environment,
LAMDERA_CACHE=off skips the Lamdera package server altogether: packages come from package.elm-lang.org and GitHub only, as with elm, and a rerouted version then fails to download.

Details · package.elm-lang.org's zip: https://github.com/andreasewering/elm-protoc-utils/zipball/1.1.0/

README About Versions Source Modules

Elm Protoc Utils

Utility functions for usage in protoc-gen-elm and your protobuf application.

Contents

Functions that are used by protoc-gen-elm's generated code (e.g. encoding JSON to bytes using Hex Encoding)
Functions that help bridge that gap between "Protobuf" Elm Types and "Standard" Elm Types (e.g. timestampToPosix)

Why an extra package?

I do not want protoc-gen-elm to generate lots of code but some tasks are pretty complex. One option would be to generate utility functions like this package but only if they are used, however, this pushes a lot of complexity towards the code generator, especially for more complicated functions that should be tested as well. This also enables us to use sub-dependencies. See it this way: if protoc-gen-elm generated code that used 3 sub-dependencies, you would to manually have to add these dependencies to your elm.json file. This way, you (hopefully) only need to add this one.

Modules