Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Backport field tag customization and media type customization from oapi-codegen-exp

Aberta
  • Algo errado?
#2,368 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
45/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Pouca atividade
Stack de tecnologia
go
Domínio
backend-api-design, tooling

Direção de pesquisa

The issue involves backporting field tag customization and media type customization from the experimental repository oapi-codegen-exp. Start by examining the linked configuration.go lines (44, 37, 41) and Configuration.md sections (lines 293, 265, 275) to understand the new configuration options. Then, locate the corresponding configuration and code generation logic in the main oapi-codegen repository. The work requires modifying internal configuration structures and the code generation templates to support these customizations while preserving default behavior. Testing will involve verifying that generated models respect the new configuration options.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

We have a lot of assumptions about how fields should be tagged in generated models, and I'd like to retain current default behavior, but allow the users to override every aspect of this behavior.

In https://github.com/oapi-codegen/oapi-codegen-exp, I've allowed field tags to be fully customized, where users can insert their own field tags by looking at the name in the spec, whether the field is required, etc.
https://github.com/oapi-codegen/oapi-codegen-exp/blob/56dd39ec275d400ae5cdc1eed293719464bbf8c2/codegen/internal/configuration.go#L44[
](https://github.com/oapi-codegen/oapi-codegen-exp/blob/56dd39ec275d400ae5cdc1eed293719464bbf8c2/Configuration.md?plain=1#L293)

Likewise, we have some patterns that we match to identify a content-type as JSON or YAML or whatever, but they can't catch all cases, so I would also like to backport the implementation:

https://github.com/oapi-codegen/oapi-codegen-exp/blob/56dd39ec275d400ae5cdc1eed293719464bbf8c2/codegen/internal/configuration.go#L37
https://github.com/oapi-codegen/oapi-codegen-exp/blob/56dd39ec275d400ae5cdc1eed293719464bbf8c2/Configuration.md?plain=1#L265

https://github.com/oapi-codegen/oapi-codegen-exp/blob/56dd39ec275d400ae5cdc1eed293719464bbf8c2/codegen/internal/configuration.go#L41
https://github.com/oapi-codegen/oapi-codegen-exp/blob/main/Configuration.md?plain=1#L275

Linguagem predominante
Go
Estrelas
8.6k
Forks
1.1k
Merge médio
14h 45min
PRs com merge (30d)
29

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de oapi-codegen/oapi-codegen

Todas as issues de oapi-codegen/oapi-codegen

Issues semelhantes

Mais issues de Go

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.