Renamed to anmolitor/elm-placeholder. That is where the repository lives now. It has not been published as a package under the new name.
Versions published as andreasewering/elm-placeholder still install under that name. 4 versions of 4 come from the new location (see their notes).
Rerouted (renamed, verified). 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-placeholder.
What we checked: The repo moved to github.com/anmolitor/elm-placeholder. Rebuilt with git archive from commit e524e4b96225 of https://github.com/anmolitor/elm-placeholder (zip prefix andreasewering-elm-placeholder-e524e4b/, America/Los_Angeles times): the zip is byte-identical to the one package.elm-lang.org recorded, SHA-1 6add495ff57e525bf704a4e7755b51ece45da1a9.
The Lamdera compiler uses this copy and prints a one-line notice saying so. elm itself fails to download this version.
Details · package.elm-lang.org's zip: https://github.com/andreasewering/elm-placeholder/zipball/2.1.0/
This module allows defining placeholder parsers based on a non-supported Syntax as well as
using the internal Template type for different purposes.
Parse a String into a Template based on a Syntax.
syntax : Syntax
syntax = { startSymbol = "${", endSymbol = "}" }
parseTemplate syntax "This is ${name}s example" |> Result.map (always ())
--> Ok ()
parseTemplate syntax "This does not ${makeSense"
--> Err "TODO deadEndsToString" -- (Waiting for upstream fix in elm/parser)Get the names of the placeholders in a Template.
The names are ordered just like they are in the given template string.
parseTemplate { startSymbol = "${", endSymbol = "}" } "${first} ${snd}"
|> Result.map getPlaceholderNames
--> Ok ["first", "snd"]
parseTemplate { startSymbol = "${", endSymbol = "}" } "${blub} ${bla} ${blub}"
|> Result.map getPlaceholderNames
--> Ok ["blub", "bla", "blub"]Get the names of the placeholders in a Template, but sorted in alphabetical order and without duplicates.
parseTemplate { startSymbol = "${", endSymbol = "}" } "${blub} ${bla} ${blub}"
|> Result.map getAlphabeticalPlaceholderNames
--> Ok ["bla", "blub"]Convert a parsed Template back to its String representation.
For any template built with Syntax s,
templateToString >> parseTemplate s == identity
parseTemplate { startSymbol = "${", endSymbol = "}" } "This is ${name}s example"
|> Result.map templateToString
--> Ok "This is ${name}s example"Change placeholder keys based on index and current key.
parseTemplate { startSymbol = "{", endSymbol = "}" } "{UPPER} case"
|> Result.map (mapPlaceholders (\_ -> String.toLower) >> templateToString)
--> Ok "{upper} case"A Syntax tells the templateParser how to distinguish placeholders from regular text.
At the moment, this can only be configured by setting start and end symbol.
Parse a String into a function substituting the argument at the position marked by the Syntax.
exampleOf : Result String (String -> String)
exampleOf = parsePlaceholder1 { startSymbol = "${", endSymbol = "}" } "This is ${name}s example"
Result.map ((|>) "Andy") exampleOf
--> Ok "This is Andys example"
parsePlaceholder1 { startSymbol = "${", endSymbol = "}" } "No placeholder"
--> Err "Expected 1 placeholders, but parsed a total of 0."
parsePlaceholder1 { startSymbol = "${", endSymbol = "}" } "${multiple}${placeholders}"
--> Err "Expected 1 placeholders, but parsed a total of 2."Parse a String into a function substituting the arguments at the two positions marked by the Syntax.
Note that this function and the other parsePlaceholderN functions always substitute elements in the order
they appear in the template string. This also means that for duplicate placeholder keys, you need to use
the parsePlaceholderAlphN family of functions instead.
parsePlaceholder2 { startSymbol = "{", endSymbol = "}" } "{greeting} {target}"
|> Result.map (\f -> f "Hello" "World")
--> Ok "Hello World"Parse a String into a function substituting the arguments at the three positions marked by the Syntax.
Parse a String into a function substituting the arguments at the four positions marked by the Syntax.
Parse a String into a function substituting the argument at all positions marked with the same, only key
This differs from parsePlaceholder1 as you can see in the following example:
syntax : Syntax
syntax = { startSymbol = "{", endSymbol = "}" }
parsePlaceholder1 syntax "{greeting} {greeting}"
--> Err "Expected 1 placeholders, but parsed a total of 2."
parsePlaceholderAlph1 syntax "{greeting} {greeting}" |> Result.map ((|>) "Hello")
--> Ok "Hello Hello"Parse a String into a function substituting the arguments at all positions marked with the two placeholder keys.
The arguments for the keys are expected in alphabetical order.
This differs from parsePlaceholder2 as you can see in the following example:
syntax : Syntax
syntax = { startSymbol = "{", endSymbol = "}" }
parsePlaceholder2 syntax "{greeting} {friend}" |> Result.map (\f -> f "Hello" "World")
--> Ok "Hello World"
parsePlaceholderAlph2 syntax "{greeting} {friend}" |> Result.map (\f -> f "Hello" "World")
--> Ok "World Hello"Parse a String into a function substituting the arguments at all positions marked with the three placeholder keys.
The arguments for the keys are expected in alphabetical order.
Parse a String into a function substituting the arguments at all positions marked with the four placeholder keys.
The arguments for the keys are expected in alphabetical order.
A
Templateincludes an ordered list of placeholders and text segments.Templates guarantee thatand they can be converted back to the same
Stringrepresentation they were parsed from.