From aedb65e04a39250ab628796916d99d9ff545f11d Mon Sep 17 00:00:00 2001
From: Dharmesh Makvana <212810347+n3orma@users.noreply.github.com>
Date: Thu, 1 Oct 2026 09:53:22 +0530
Subject: [PATCH] document loadRegistry exported objects behavior

Document that loadRegistry() automatically loads objects previously exported with batchExport() into the global environment.

The documentation now also notes that existing objects with the same names may be overwritten, making the behavior clearer to users.
---
 R/loadRegistry.R | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/R/loadRegistry.R b/R/loadRegistry.R
index 27dbfd19..f970ba51 100644
--- a/R/loadRegistry.R
+++ b/R/loadRegistry.R
@@ -3,6 +3,10 @@
 #' @description
 #' Loads a registry from its \code{file.dir}.
 #'
+#' Objects previously exported with \code{\link{batchExport}} are automatically
+#' loaded into the global environment when the registry is loaded. Existing
+#' objects with the same names may be overwritten.
+#'
 #' Multiple R sessions accessing the same registry simultaneously can lead to database inconsistencies.
 #' This is especially dangerous if the same \code{file.dir} is accessed from multiple machines, e.g. via a mount.
 #'