Running yardoc after deleting/moving a class does not remove the generated HTML file for that class

[sam-carlberg]

Steps to reproduce

Tested and reproduced in both a large legacy project and in a small proof-of-concept project

This is the minimal reproduction for the issue. I've done my best to remove all extraneous code and unique environment state on my machine before providing these steps:

1. Create a new class (echo "class Foo; end" > lib/foo.rb)
2. Run yardoc to generate documentation for the new class
3. Observe doc/Foo.html was created
4. Delete the class (rm lib/foo.rb)
5. Run yardoc again
6. Observe doc/Foo.html still exists

Actual Output

doc/Foo.html still persists lib/foo.rb is removed from .yardoc/checksums Foo is removed from the class list on the index page

Expected Output

doc/Foo.html should be deleted lib/foo.rb is removed from .yardoc/checksums Foo is removed from the class list on the index page

Environment details:

• OS: macOS Monterey (12.0.1)
• Ruby version (ruby -v): ruby 2.6.6p146
• YARD version (yard -v): yard 0.9.27
• Relevant software dependency/versions: N/A

I have read the Contributing Guide.

[lsegal]

This is expected behavior. In order to avoid making any dangerous unrecoverable mistakes with your filesystem, YARD will never remove files in the output directory.

If you're rerunning YARD generation, it's up to you to clear the directory beforehand if that is required.

[sam-carlberg]

Thanks for the clarification @lsegal