9aa85d8e5d
CI / test (pull_request) Failing after 2m13s
- Rewrite README.md with overview, features, installation (go install +
build from source), quick start, full CLI flag reference table,
output section descriptions, project structure, and development guide
- Add package-level doc comments to all five internal packages:
config, dns, fingerprint, output, traverse (via doc.go or existing
package-declaration files)
- Add GoDoc comments on every exported type, constant, function, and
method across all packages:
- internal/config: Config struct fields, all Parse*/Default/Validate
- internal/dns: QueryConfig, Resolver, BasicResolver, CachingResolver,
ExchangeFunc, RootServer, RootDiscoveryConfig, DecodedResponse,
ResponseClassification, all exported helpers
- internal/fingerprint: Fingerprinter, New, NewWithTimeout, Query,
FingerprintAll
- internal/traverse: Traverser, TraverserConfig, TraversalResult,
Referral, ResolutionState, Response, ResponseType, InfoCache,
Stack, TraverserHooks, EventStage, TraversalEvent, EventHandler,
CircularReferralError, UnresolvableNameserverError
- internal/output: Format, Config, Formatter, SummaryStats,
NewFormatter, AttachHooks, RunTraversal, DefaultConfig,
ComputeSummary
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: multica-agent <github@multica.ai>
12 lines
543 B
Go
12 lines
543 B
Go
// Package config defines the ExploreDNS runtime configuration, flag parsing
|
|
// helpers, input validation, and usage text.
|
|
//
|
|
// Config holds all settings that control traversal behaviour and output.
|
|
// DefaultConfig returns a ready-to-use Config with sensible defaults.
|
|
// After populating Config from CLI flags, call Validate to ensure
|
|
// all field values are within their accepted ranges.
|
|
//
|
|
// Helper functions such as ParseQueryType, ParseDebugLevel, and
|
|
// ParseRootServer are pure converters; they never read flag state.
|
|
package config
|