Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

allow accessBeginAt to be nullable in setAccessBeginAtAsync #122

Merged
merged 1 commit into from
Dec 2, 2024
Merged

allow accessBeginAt to be nullable in setAccessBeginAtAsync #122

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions ...rc/main/kotlin/com/open200/xesar/connect/extension/XesarConnectIdentificationMediumExt.kt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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?,
requestConfig: XesarConnect.RequestConfig = buildRequestConfig()
): SingleEventResult<MediumChanged> {
return sendCommandAsync<SetAccessBeginAtMapi, MediumChanged>(
Expand Down