mirror of
https://github.com/kubernetes/node-problem-detector.git
synced 2026-08-21 13:16:35 +00:00
Bruno Chauvet
877b6d6908
- Update github.com/sirupsen/logrus v1.9.0 -> v1.9.3 in test/go.mod to fix GHSA-4f99-4q7p-p3gh (High) - Update github.com/prometheus/prometheus v0.35.0 -> v0.311.3 to fix GHSA-vffh-x6r8-xx99 (Medium) - Run go mod tidy and go mod vendor to update vendor directory
26 lines
1010 B
Go
26 lines
1010 B
Go
// SPDX-FileCopyrightText: Copyright 2015-2025 go-swagger maintainers
|
|
// SPDX-License-Identifier: Apache-2.0
|
|
|
|
// Package mangling provides name mangling capabilities.
|
|
//
|
|
// Name mangling is an important stage when generating code:
|
|
// it helps construct safe program identifiers that abide by the language rules
|
|
// and play along with linters.
|
|
//
|
|
// Examples:
|
|
//
|
|
// Suppose we get an object name taken from an API spec: "json_object",
|
|
//
|
|
// We may generate a legit go type name using [NameMangler.ToGoName]: "JsonObject".
|
|
//
|
|
// We may then locate this type in a source file named using [NameMangler.ToFileName]: "json_object.go".
|
|
//
|
|
// The methods exposed by the NameMangler are used to generate code in many different contexts, such as:
|
|
//
|
|
// - generating exported or unexported go identifiers from a JSON schema or an API spec
|
|
// - generating file names
|
|
// - generating human-readable comments for types and variables
|
|
// - generating JSON-like API identifiers from go code
|
|
// - ...
|
|
package mangling
|