From b85a2d6f9f2c87e17aa9f2c77e031002c12c1d57 Mon Sep 17 00:00:00 2001 From: Peeter Piegaze <1153481+ppiegaze@users.noreply.github.com> Date: Thu, 25 Jul 2024 11:52:51 +0200 Subject: [PATCH] try anchor links again Signed-off-by: Peeter Piegaze <1153481+ppiegaze@users.noreply.github.com> --- docs/conf.py | 1 + docs/user_guide/development_lifecycle/caching.md | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/conf.py b/docs/conf.py index a729b9330c..6ef6e93a1c 100644 --- a/docs/conf.py +++ b/docs/conf.py @@ -294,6 +294,7 @@ } myst_enable_extensions = ["colon_fence"] +myst_heading_anchors = 6 # Sphinx-mermaid config mermaid_output_format = "raw" diff --git a/docs/user_guide/development_lifecycle/caching.md b/docs/user_guide/development_lifecycle/caching.md index c2e1f8caab..cdb986ef4a 100644 --- a/docs/user_guide/development_lifecycle/caching.md +++ b/docs/user_guide/development_lifecycle/caching.md @@ -30,7 +30,7 @@ To enable caching set `cache=True`. A change to this parameter will invalidate the cache. This allows you to explicitly indicate when a change has been made to the task that should invalidate any existing cached results. Note that this is not the only change that will invalidate the cache (see below). -Also, note that you can manually trigger cache invalidation per execution using the `overwrite-cache` flag. +Also, note that you can manually trigger cache invalidation per execution using the [`overwrite-cache` flag](#overwrite-cache-flag). * `cache_serialize` (`bool`): Enables or disables [cache serialization](./cache_serializing). When enabled, Flyte ensures that a single instance of the task is run before any other instances that would otherwise run concurrently. This allows the initial instance to cache its result and lets the later instances reuse the resulting cached outputs.