[go-nuts] Re: OpenAPI and Go

2025-03-07 Thread Christoph Berger
I briefly examined four approaches a while ago (https://appliedgo.net/spotlight/4-tools-for-generating-rest-apis/)—two spec-to-code and two code-to-spec approaches. I still found no time to run deeper experiments with any of them, though. On Monday, March 3, 2025 at 11:01:45 AM UTC+1 Alex Pliu

[go-nuts] Re: OpenAPI and Go

2025-03-07 Thread Hannah Bamgbelu
This is a cry for help! I cannot seem to go forward in my Go lessons. I am very stuck in APIs. As I do not have prior experience in this, it is so disheartening because this is something I need to learn On Tuesday, March 4, 2025 at 7:03:05 AM UTC+1 Shaun Houlihan wrote: > Hi Alex, > > Yes, I us

[go-nuts] Re: OpenAPI and Go

2025-03-07 Thread Sergey Mogilnikov
API-first, create specification, than generate all the code with ogen. - https://github.com/ogen-go/ogen Generate models, controllers, etc. Fully compatible with std `http` lib. пятница, 7 марта 2025 г. в 12:48:03 UTC+3, Christoph Berger: > I briefly examined four approaches a while ago ( > ht

Re: [go-nuts] go-contrib-init error message

2025-03-07 Thread Ian Lance Taylor
On Fri, Mar 7, 2025 at 12:03 AM Patrick wrote: > > I'd like to contribute to https://go.googlesource.com/text. So I cloned the > directory and ran (after registering and logging in) > > go-contrib-init > > and the resulting message is: > > Current directory's git was cloned from "https://go.googl

[go-nuts] go-contrib-init error message

2025-03-07 Thread Patrick
Hello all, I'd like to contribute to https://go.googlesource.com/text. So I cloned the directory and ran (after registering and logging in) go-contrib-init and the resulting message is: Current directory's git was cloned from "https://go.googlesource.com/text";; origin should be "https://go.g

[go-nuts] `golang.org/x/tools/go/packages: unexpected new packages during load` when upgrading to 1.24.1

2025-03-07 Thread Samuel Littley
I've been working on upgrading my company's code repository from 1.23.6 to 1.24.1, and have found that running gosec now fails with an error like panic: golang.org/x/tools/go/packages: unexpected new packages during load of (full output at the end of this me

Re: [go-nuts] `golang.org/x/tools/go/packages: unexpected new packages during load` when upgrading to 1.24.1

2025-03-07 Thread 'Jim Idle' via golang-nuts
It look like gosec can be told what version of Go it inspecting. The error sounds like it is saying that this package is not known to it, which would make sense if somewhere you have told it it is inspecting 1.23.6 as then this would be an unexpected package in that version of Go. Have you up