@@ -165,11 +165,16 @@ defmodule Mix.Tasks.Docs do
165
165
See the "Changing documentation over time" section below for more.
166
166
167
167
* `:skip_undefined_reference_warnings_on` - ExDoc warns when it can't create a `Mod.fun/arity`
168
- reference in the current project docs e.g. because of a typo. This list controls where to
169
- skip the warnings, for a given module/function/callback/type (e.g.: `["Foo", "Bar.baz/0"]`)
170
- or on a given file (e.g.: `["pages/deprecations.md"]`). This option can also be a function
171
- from a reference string to a boolean (e.g.: `&String.match?(&1, ~r/Foo/)`);
172
- default is nothing to be skipped.
168
+ reference in the current project docs (for example, because of a typo). This option controls when to
169
+ skip such warnings. This option can be a list of strings that will be checked for exact matches,
170
+ or a function that takes a *reference* and must return a boolean (`true` means "skip this").
171
+ *References* that are checked against this option (either whether they're in the given
172
+ list or whether they match the given function) are the relative filename, the "ID" of
173
+ the node (like `User.exists?/1`), or the module name. Examples for this option:
174
+ * `["Foo", "Bar.baz/0"]` - skip warnings for `Foo` and `Bar.baz/0`
175
+ * `&String.match?(&1, ~r/Foo/)` - skip warnings for any reference that matches the regex
176
+ * `["pages/deprecations.md"]` - skip warnings for any reference in the
177
+ `pages/deprecations.md` file
173
178
174
179
* `:skip_code_autolink_to` - Similar to `:skip_undefined_reference_warnings_on`, this option
175
180
controls which terms will be skipped by ExDoc when building documentation.
0 commit comments