René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"OAS3.1.0 const naming is long and different than other types","articleBody":"I have a simple oas3 file v3.1.0 with both const and regular objects. Here is my config `cfg-schemas.yaml`:\n\n```yaml\npackage: api\ngenerate:\n  models: true\noutput: go/api/schemas.go\noutput-options:\n  skip-prune: true\n  name-normalizer: ToCamelCaseWithInitialisms\n  yaml-tags: true\n```\n\nAnd my schemas input file (simplified) `schemas.yaml`:\n\n```yaml\nopenapi: \"3.1.0\"\ncomponents:\n  schemas:\n    SomeConst:\n      type: string\n      const: \"someconststringinput/fields/aes256\"\n    OtherConst:\n      type: string\n      const: \"otherconststringinput/subdata/ed25519\"  \n    Metadata:\n      type: object\n      properties:\n        name:\n          type: string\n          description: name of the input\n        description:\n          type: string\n          description: description of the input\n        digest:\n          type: string\n          description: SHA256 digest of the input\n```\n\nAnd then I run:\n\n```\noapi-codegen -config ./cfg-schemas.yaml ./schemas.yaml\n```\n\nThe output I get is the following:\n\n```go\n// Package api provides primitives to interact with the openapi HTTP API.\n//\n// Code generated by github.com/oapi-codegen/oapi-codegen/v2 version v2.8.0 DO NOT EDIT.\npackage api\n\n// Defines values for OtherConst.\nconst (\n        OtherconststringinputSubdataEd25519 OtherConst = \"otherconststringinput/subdata/ed25519\"\n)\n\n// Valid indicates whether the value is a known member of the OtherConst enum.\nfunc (e OtherConst) Valid() bool {\n        switch e {\n        case OtherconststringinputSubdataEd25519:\n                return true\n        default:\n                return false\n        }\n}\n\n// Defines values for SomeConst.\nconst (\n        SomeconststringinputFieldsAes256 SomeConst = \"someconststringinput/fields/aes256\"\n)\n\n// Valid indicates whether the value is a known member of the SomeConst enum.\nfunc (e SomeConst) Valid() bool {\n        switch e {\n        case SomeconststringinputFieldsAes256:\n                return true\n        default:\n                return false\n        }\n}\n\n// Metadata defines model for Metadata.\ntype Metadata struct {\n        // Description description of the input\n        Description *string `json:\"description,omitempty\" yaml:\"description,omitempty\"`\n\n        // Digest SHA256 digest of the input\n        Digest *string `json:\"digest,omitempty\" yaml:\"digest,omitempty\"`\n\n        // Name name of the input\n        Name *string `json:\"name,omitempty\" yaml:\"name,omitempty\"`\n}\n\n// OtherConst defines model for OtherConst.\ntype OtherConst string\n\n// SomeConst defines model for SomeConst.\ntype SomeConst string\n```\n\nNotice that my `Metadata` component becomes `type Metadata struct`, while my peer `SomeConst` constant become `type SomeConst string` which can be access via the painfully named `SomeconststringinputFieldsAes256 SomeConst = \"someconststringinput/fields/aes256\"`.\n\nSince this is a constant, I don't care much to create a `type SomeConst` which is just a `string`, and then have a single object with a long name `SomeconststringinputFieldsAes256` (looks like derived from the const value?) for it. I really am just looking for the simple:\n\n```go\nconst SomeConst = \"someconststringinput/fields/aes256\"\n```\n\nI hope this describes the issue well?","author":{"url":"https://github.com/deitch","@type":"Person","name":"deitch"},"datePublished":"2026-09-29T16:17:05Z","url":"https://github.com/oapi-codegen/oapi-codegen/issues/2596"}