From b93f70bae49dfbdeb1555b5cd8cd35aedcf3fbd8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Yann=20C=C3=A9bron?= Date: Mon, 28 Oct 2024 16:03:16 +0100 Subject: [PATCH] stub_indexes.md: improve warning about stale keys --- topics/basics/indexing_and_psi_stubs/stub_indexes.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/topics/basics/indexing_and_psi_stubs/stub_indexes.md b/topics/basics/indexing_and_psi_stubs/stub_indexes.md index 0dc4cf55b..30660c3fa 100644 --- a/topics/basics/indexing_and_psi_stubs/stub_indexes.md +++ b/topics/basics/indexing_and_psi_stubs/stub_indexes.md @@ -108,7 +108,11 @@ To access the data from an index, the following instance methods are used on the `AbstractStubIndex.getAllKeys()/processAllKeys()` returns the list of all keys (processes all keys) in the index for the specified project (for example, the list of all class names found in the project). -> NOTE: These may return stale/out-of-date data. See [](#elements) to obtain/verify actual existing elements for the given key (e.g., when iterating all keys to collect completion variants). +> The returned keys may return stale/out-of-date data. +> See [](#elements) to obtain/verify actual existing elements for the given key in a given scope +> (for example, when iterating all keys to collect relevant completion variants). +> +{style="warning" title="Stale Data"} #### Elements