From f57505d77494d060c334211325c1387c18d5c723 Mon Sep 17 00:00:00 2001 From: "J. Nick Koston" Date: Tue, 24 May 2022 16:24:00 -0500 Subject: [PATCH] Document removal of entity_matches_only from logbook api (#1340) Co-authored-by: Franck Nijhof --- .../2022-05-24-entity_matches_only_removed_logbook_card.md | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 blog/2022-05-24-entity_matches_only_removed_logbook_card.md diff --git a/blog/2022-05-24-entity_matches_only_removed_logbook_card.md b/blog/2022-05-24-entity_matches_only_removed_logbook_card.md new file mode 100644 index 00000000..07669f5d --- /dev/null +++ b/blog/2022-05-24-entity_matches_only_removed_logbook_card.md @@ -0,0 +1,7 @@ +--- +author: J. Nick Koston +authorURL: https://github.com/bdraco +title: "Logbook API removal of `entity_matches_only` flag" +--- + +Before 2022.6, the `entity_matches_only` flag prevented the logbook from providing context data in exchange for performance improvement when querying specific entities. Selecting the context data for particular entities is no longer an intensive process with the new logbook design. No immediate action is required as the flag will be ignored, and removing the flag from any active code paths can be done at your leisure. \ No newline at end of file