Clarify NfQueue (config field) vs NfQeueue (verdict constant) #74
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
keyop-go/nfq_forwarder!74
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue41_clarify_nfqueue_vs_nfqeueue"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #41
Background
Investigated (with results posted to #41 and MR !73) whether
NfQeueuewas a Claude-introduced typo. It isn't:github.com/florianl/go-nfqueue@v1.3.2genuinely exports its verdict constant misspelled asNfQeueue(confirmed directly from the vendored module source,types.go). The same package separately exports a correctly spelled, unrelated identifier -Config.NfQueue(auint16struct field for which queue number to bind to) - used once in this codebase'sinitNfqueue. A full repo grep for both spellings found every usage of each already correct for what it refers to.Change
Purely a clarifying comment at the one
NfQueue(config field) usage, explaining it's a different identifier from the verdict constantNfQeueueused elsewhere in the file, so this doesn't get mistaken for an inconsistency again.Testing
Documentation-only change -
make lint/make testboth clean, no behavior change.Related
Follow-up to #33 (MR !73, now merged) - the doc comment this one cross-references (on
setVerdict, explaining theNfQeueuelandmine) landed there.mentioned in issue #41
added 3 commits
main3d67c563- Clarify NfQueue (config field) vs NfQeueue (verdict constant) (#41)Compare with previous version
assigned to @claude
requested review from @danny
LGTM
approved this merge request
mentioned in commit
b534e34d53