Merge pull request #838 from lightninglabs/docs-lnd

Update lnd documentation

Author: github-actions[bot]

docs/lnd/development_guidelines.md

@@ -230,6 +230,48 @@ value, err := bar(
 )
 ```
 
+As long as the visual symmetry of the opening and closing parentheses is
+preserved, arguments that would otherwise introduce a new level of indentation
+are allowed to be written in a more compact form.
+
+Example with inline struct creation:
+
+**ACCEPTABLE**
+```go
+	response, err := node.AddInvoice(
+		ctx, &lnrpc.Invoice{
+			Memo:      "invoice",
+			ValueMsat: int64(oneUnitMilliSat - 1),
+		},
+	)
+```
+
+**PREFERRED**
+```go
+	response, err := node.AddInvoice(ctx, &lnrpc.Invoice{
+		Memo:      "invoice",
+		ValueMsat: int64(oneUnitMilliSat - 1),
+	})
+```
+
+Example with nested function call:
+
+**ACCEPTABLE**:
+```go
+	payInvoiceWithSatoshi(
+		t.t, dave, invoiceResp2, withFailure(
+			lnrpc.Payment_FAILED, failureNoRoute,
+        ),
+    )
+```
+
+**PREFERRED**:
+```go
+	payInvoiceWithSatoshi(t.t, dave, invoiceResp2, withFailure(
+		lnrpc.Payment_FAILED, failureNoRoute,
+	))
+```
+
 #### Exception for log and error message formatting
 
 **Note that the above guidelines don't apply to log or error messages.** For

docs/lnd/release-notes/release-notes-0.19.0.md

@@ -128,6 +128,9 @@ when running LND with an aux component injected (custom channels).
   such that the probability is evaluated quicker and to be more accurate in
   outdated scenarios.
 
+* [Fix a bug](https://github.com/lightningnetwork/lnd/pull/9798) that could
+  result in a new topology client missing a channel-close notifications. 
+
 # New Features
 
 * Add support for [archiving channel backup](https://github.com/lightningnetwork/lnd/pull/9232)