fix: allow accessBeginAt to be nullable in setAccessBeginAtAsync

Allowing accessBeginAt to be nullable lets Xesar set the access begin for an identification medium
open200 · Dec 2, 2024 · 2013c08 · 2013c08
1 parent 3fdc1f3
commit 2013c08
Showing 1 changed file with 3 additions and 2 deletions.
diff --git a/...rc/main/kotlin/com/open200/xesar/connect/extension/XesarConnectIdentificationMediumExt.kt b/...rc/main/kotlin/com/open200/xesar/connect/extension/XesarConnectIdentificationMediumExt.kt
@@ -216,12 +216,13 @@ suspend fun XesarConnect.removeZoneAuthorizationFromMediumAsync(
  * Sets the access begin of an identification medium asynchronously.
  *
  * @param mediumId The ID of the medium to set the access begin.
- * @param accessBeginAt The access begin to set.
+ * @param accessBeginAt The access begin to set (optional). If the parameter is null, the access
+ *   begin is automatically set to the current LocalDateTime minus 2 hours by Xesar.
  * @param requestConfig The request configuration (optional).
  */
 suspend fun XesarConnect.setAccessBeginAtAsync(
     mediumId: UUID,
-    accessBeginAt: LocalDateTime,
+    accessBeginAt: LocalDateTime? = null,
     requestConfig: XesarConnect.RequestConfig = buildRequestConfig()
 ): SingleEventResult<MediumChanged> {
     return sendCommandAsync<SetAccessBeginAtMapi, MediumChanged>(