@@ -15,7 +15,8 @@ You will need to enable the `--pre` flag if you're installing the latest version
1515
1616Simplest invocation:
1717
18- $ elm-doc . --output docs --fake-license 'SPDX license name'
18+ $ elm-doc . --output docs --fake-license 'SPDX license name' \
19+ --elm-path path/to/usually/node_modules/.bin/elm
1920
2021The license name is required because elm-doc uses the official Elm binary to
2122validate and generate docs; the official Elm binary only generates
@@ -41,16 +42,10 @@ and `--fake-version`.
4142elm-doc creates a build directory named ` .elm-doc ` at the root of the project.
4243You may want to ignore it in your SCM config, or you can change its path with ` --build-dir ` .
4344
44- You can further point ` --elm-path ` at your existing installation of ` elm ` binary
45- to avoid the overhead of installing Elm:
46-
47- $ elm-doc . --output docs \
48- --elm-path ui/node_modules/.bin/elm
49-
5045` --validate ` can check if you have all the necessary documentation in place:
5146
5247 $ elm-doc . \
53- --elm-path ui /node_modules/.bin/elm \
48+ --elm-path . /node_modules/.bin/elm \
5449 --validate
5550
5651` elm-doc ` assumes you're working on an app, not a package; it will try to generate
@@ -59,13 +54,13 @@ documentation for all modules found in the application source directories.
5954You can ` --exclude-modules ` by using [ fnmatch] ( https://docs.python.org/3/library/fnmatch.html )
6055patterns:
6156
62- $ elm-doc . --output docs \
63- --elm-path ui /node_modules/.bin/elm \
57+ $ elm-doc . --output docs --fake-license 'SPDX license name' \
58+ --elm-path . /node_modules/.bin/elm \
6459 --exclude-modules '*.Private.*,Blacklist.*'
6560
6661or ` --exclude-source-directories ` entirely:
6762
68- $ elm-doc . --output docs \
63+ $ elm-doc . --output docs --fake-license 'SPDX license name' \
6964 --elm-path ui/node_modules/.bin/elm \
7065 --exclude-source-directories generated
7166
@@ -78,7 +73,7 @@ You can also specify which files and directories to _include_ in the list of mod
7873Note that the ` --exclude ` flag takes no effect if you explicitly specify which
7974files to include, unless you add the ` --force-exclusion ` flag:
8075
81- $ elm-doc . --output docs \
76+ $ elm-doc . --output docs --fake-license 'SPDX license name' \
8277 --elm-path ui/node_modules/.bin/elm \
8378 --exclude-modules '*.Private.*,Blacklist.*' \
8479 --force-exclusion \
@@ -104,9 +99,9 @@ This is the rough build process:
10499 - Populate ` --fake-* ` fields, including the license: these are required for a package project but not included in an application project's elm.json
105100 - Add dependencies that are listed as popular packages in the sidebar, making HTTP requests to look up the latest versions
106101 - This means the actual build / validation process will have its own elm-stuff directory
107- - Copy source files into the build directory's ` src ` directory using [ dirsync ] ( https://bitbucket.org/tkhyn/dirsync/ )
102+ - Copy source files into the build directory's ` src ` directory using rsync
108103 - An application project supports multiple source directories, while a package project supports only ` src `
109- - For each file that were copied, rewrite port delcarations to be normal functions
104+ - For each file that was copied, rewrite port delcarations to be normal functions
110105 - This is needed because ports are not allowed in package projects
111106- Run ` elm make ` with the ` --doc ` flag on
112107- If validating docs, exit here
0 commit comments