Renamed to henriquecbuss/elm-eos. It is published under that name, and new versions come out there.
Versions published as NeoVier/elm-eos still install under that name. 1 version of 1 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/henriquecbuss/elm-eos.
What we checked: The repo moved to github.com/henriquecbuss/elm-eos and tag 1.0.0 is there; its commit 12b679fbd416 is from 2022-11-04 12:13 UTC, after the version was published (2022-11-04 02:04 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/NeoVier/elm-eos/zipball/1.0.0/
Permissions control what EOSIO accounts can do and how actions are authorized.
They are organized in a hierarchical structure, with the root permission being
the Owner permission. The Active permission is a child of the Owner.
Turn a permission into a JSON value.
Decode a JSON value into a Permission
There are two permissions by default: Owner and Active. However, each account may have arbitrary permissions (that's what
Customis for).