npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

elm-doc-test

v4.0.0

Published

doc-test for elm

Downloads

22

Readme

elm-doc-test Build Status

Verify examples in your docs.

Install

$ npm i elm-test -g
$ npm i elm-doc-test -g
$ elm-test init

Setup

$ touch tests/elm-doc-test.json

elm-doc-test.json contains information on which files contain verified examples and where to find them.

{
  "root": "../src",
  "tests": [
    "Mock",
    "Mock.Foo.Bar.Moo"
  ]
}

It's recommended to add ./tests/Doc to your .gitignore.

Writing Verified Examples

Verified examples look like normal code examples in doc-comments.
Code needs to be indented by 4 spaces. You can specify the expected result of an expression, by adding a comment --> (the > is important) and an expected expression.

{-| returns the sum of two int.

    -- You can write the expected result on the next line,

    add 41 1
    --> 42

    -- or on the same line.

    add 3 3 --> 6

-}
add : Int -> Int -> Int
add =
    (+)

You can write examples on multiple lines.

{-| reverses the list

    rev
        [ 41
        , 1
        ]
    --> [ 1
    --> , 41
    --> ]

    rev [1, 2, 3]
        |> List.map toString
        |> String.join ""
    --> "321"
-}
rev : List a -> List a
rev =
    List.reverse

You can specify imports, if you want to use a module or a special test util.

{-|
    import Dict

    myWeirdFunc (Dict.fromList [(1, "a"), (2, "b")]) [2, 1]
    --> "ba"
-}

Running DocTests

elm-doc-test only converts your doc-tests into elm-tests. You have to use elm-test in order to run them.

$ elm-doc-test && elm-test tests/Doc/Main.elm

By default the first command creates the tests at tests/Doc/. If you want to have them at a custom location use the --output argument (e.g. elm-doc-test --output my/custom/path/ will create the tests at my/custom/path/Doc/).

Also by default the first command looks for the config file at tests/elm-doc-test.json. If you want it to load a specific config file use the --config argument (e.g. elm-doc-test --config my/custom/path/elm-doc-test.json will read the config from my/custom/path/elm-doc-test.json).

Examples

You can run the examples using:

npm start