First pass at incremental dirtyreload

[jkaye2012]

Rough sketch of how we may approach supporting incremental dirty reload. Currently, this enables incremental mode only if two conditions are met:

1. The server is being run with --dirtyreload enabled
2. build_docs_dir was supplied by the user

The second condition exists because I think it's required for something like this to work; without it, mkdocs won't have access to the generated build files (I think). Incremental mode also disables merging beyond the first run right now, but I'm not 100% sure if that's correct either.

[athackst]

Thanks for this!

I don't think (2) is strictly needed - the plugin updates the docs directory to the tmp build one.

It looks like there was some issues with mkdocs clearing settings when reloading configs to ignore the site dir and continually appending extracted docs instead of overwriting them.

I've taken your base and addressed these in #446

LMK if it works for you and I'll merge it in!

[jkaye2012]

Great! I should have time to test this out on Thursday or Friday this week - traveling for the holidays right now. Will let you know then.

…

On Mon, Dec 26, 2022, 7:23 PM Allison Thackston ***@***.***> wrote: Thanks for this! I don't think (2) is strictly needed - the plugin updates the docs directory to the tmp build one. It looks like there was some issues with mkdocs clearing settings when reloading configs to ignore the site dir and continually appending extracted docs instead of overwriting them. I've taken your base and addressed these in #446 <#446> LMK if it works for you and I'll merge it in! — Reply to this email directly, view it on GitHub <#442 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7FL7BIBHNS7GTTF5JKJ43WPJHJ7ANCNFSM6AAAAAATHIRTCY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[jkaye2012]

Resolved in #446