What changed, and why it matters
This commit only fixes a typo in a code comment, changing the name 'HasLightningNode' to 'HasNode' so it matches the actual function name. No code behavior was changed and there is no security impact.
No action required; this is a non-functional documentation-only change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff updates the Go doc comment for KVStore.HasNode in graph/db/kv_store.go. The previous comment referenced a non-existent method HasLightningNode; the comment now correctly names HasNode. The function signature and implementation are untouched.
Changed components
graph/db/kv_store.goInspect captured patch +4 / −5
diff --git a/graph/db/kv_store.go b/graph/db/kv_store.go
index c8e6151..5e94665 100644
--- a/graph/db/kv_store.go
+++ b/graph/db/kv_store.go
@@ -3431,11 +3431,10 @@ func (c *KVStore) fetchLightningNode(tx kvdb.RTx,
return node, nil
}
-// HasLightningNode determines if the graph has a vertex identified by the
-// target node identity public key. If the node exists in the database, a
-// timestamp of when the data for the node was lasted updated is returned along
-// with a true boolean. Otherwise, an empty time.Time is returned with a false
-// boolean.
+// HasNode determines if the graph has a vertex identified by the target node
+// identity public key. If the node exists in the database, a timestamp of when
+// the data for the node was lasted updated is returned along with a true
+// boolean. Otherwise, an empty time.Time is returned with a false boolean.
func (c *KVStore) HasNode(_ context.Context,
nodePub [33]byte) (time.Time, bool, error) {
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.