NOTE: the latest version is 1.0.2

Rerouted (retagged, needs approval). The tag now points at a different commit than when this version was published. The Lamdera package server serves a copy recovered from https://github.com/Yagger/elm-review-no-url-string-concatenation.

What we checked: Tag 1.0.0 is still on github.com/Yagger/elm-review-no-url-string-concatenation; its commit 1168c366e69a is from 2021-10-01 12:40 UTC, after the version was published (2021-10-01 12:33 UTC); elm.json is byte-identical to 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/Yagger/elm-review-no-url-string-concatenation/zipball/1.0.0/

README About Versions Source Modules

NoUrlStringConcatenation

rule : Rule

Reports expressions concatenating strings with forward slash

config =
    [ NoUrlStringConcatenation.rule
    ]

Fail

a =
    `baseUrl ++ "/intros/" ++ introId`

Success

a =
    `Url.Builder.crossOrigin baseUrl [ "intros", "introId" ]`

When (not) to enable this rule

This rule is useful when there are many expressions that build URL using string concatenation. This rule is not useful when there are plenty of expressions concatenating non-url strings that contain forward slash.

Try it out

You can try this rule out by running the following command:

elm-review --template undefined/example --rules NoUrlStringConcatenation

Modules