How to filter out errors due to alias of Type name when building documentation?

For example, the summary of objects of type Array{T,1} has been changed to Vector{T} in julia1.6. This makes the documentation build of a package fail on nightly. I wonder if there is a way to insert the correct output in the index.md file, so that the documentation build passes on all versions? I am trying to locate potential documentation breakages introduced by a feature, and would like to filter out errors due to this change in display style.

How to tell Documenter to treat these two styles as aliases that are equivalent? I don’t want to ignore the output altogether.

You can use doctest filters, see Documenter’s manual, but I would instead recommend building the documentation on just one julia version.

2 Likes