From 56352c51c8b11241b1f79e7a1cc3aef2681b1639 Mon Sep 17 00:00:00 2001 From: Luca Weiss Date: Fri, 16 Aug 2024 10:36:27 +0200 Subject: [PATCH] docs: Add parameters for 'notification process' (#144) Make sure it's visible in the usage documentation that these parameters exist since they make life easier. Fixes #127 Co-authored-by: Luca Weiss --- docs/USAGE.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/docs/USAGE.md b/docs/USAGE.md index 59a9354..c0f5c01 100644 --- a/docs/USAGE.md +++ b/docs/USAGE.md @@ -272,7 +272,7 @@ lpac notification [parameters] ``` > [!NOTE] -> Downstream developers or end users should process Notification as soon as possible when they exist to comply with GSMA specifications. lpac will not automatically delete the Notification after sending it, and you need to delete it manually. +> Downstream developers or end users should process Notification as soon as possible when they exist to comply with GSMA specifications. lpac will not automatically delete the Notification after sending it. You can pass `-r` to `notification process` or you need to delete it manually.
@@ -314,6 +314,13 @@ lpac notification [parameters]
+##### Processing requires connection to server and the following optional parameters: + +The following parameters can be used to customize the behavior of `notification process`: + +- `-a`: Process all notifications +- `-r`: Automatically remove processed notifications + #### driver Now there is only one command: `lpac driver apdu list` to get card reader list.