Renamed to finos/morphir-elm. It is published under that name, and new versions come out there.
Versions published as Morgan-Stanley/morphir-elm still install under that name. 5 versions of 5 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/finos/morphir-elm.
What we checked: The repo moved to github.com/finos/morphir-elm and tag 3.0.0 is there; its commit 5fb93bcdc077 is from 2020-10-29 14:07 UTC, after the version was published (2020-08-17 21:31 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/Morgan-Stanley/morphir-elm/zipball/3.0.0/
Helpers to work with composite keys.
It is difficult to work with composite keys in Elm due to various limitations:
This library resolves those issues by introducing type aliases for keys of various element sizes. All these types are comparable and they all have utility functions to compose them. Here's an example:
type alias MyEntity =
{ foo : String
, bar : Int
, baz : Float
}
-- myKey : Key3 Int String Float
myKey =
key3 .bar .foo .bazNote: This file was generated using Elm code that is included as a comment at the end of the source code for this module. You can use that code to extend this module without too much manual work.
Creates a key with zero elements.
Create a composite key with 2 elements.
Create a composite key with 3 elements.
Create a composite key with 4 elements.
Create a composite key with 5 elements.
Create a composite key with 6 elements.
Create a composite key with 7 elements.
Create a composite key with 8 elements.
Create a composite key with 9 elements.
Create a composite key with 10 elements.
Create a composite key with 11 elements.
Create a composite key with 12 elements.
Create a composite key with 13 elements.
Create a composite key with 14 elements.
Create a composite key with 15 elements.
Create a composite key with 16 elements.
Type that represents a zero element key. The ideal representation would be () but Unit is not comparable in Elm.
So we use Int to retain comparable semantics but only 0 should be used as a value.
key0 and noKey can be used to create a Key0 value.
Type that represents a composite key with 2 elements.
Type that represents a composite key with 3 elements.
Type that represents a composite key with 4 elements.
Type that represents a composite key with 5 elements.
Type that represents a composite key with 6 elements.
Type that represents a composite key with 7 elements.
Type that represents a composite key with 8 elements.
Type that represents a composite key with 9 elements.
Type that represents a composite key with 10 elements.
Type that represents a composite key with 11 elements.
Type that represents a composite key with 12 elements.
Type that represents a composite key with 13 elements.
Type that represents a composite key with 14 elements.
Type that represents a composite key with 15 elements.
Type that represents a composite key with 16 elements.
Creates a key with zero elements.