spaasis

Just chiming in from JetBrains Rider using Continue 0.0.56. My root level .gitignore has the following: ``` # Build results ... [Bb]in/ [Oo]bj/ ... ``` Yet the sqlite index contains...

Just having ``` services .AddOpenApi("v1) .AddOpenApi("v2) .AddApiVersioning(opt => { opt.ReportApiVersions = true; }).AddApiExplorer(options => { options.GroupNameFormat = "'v'VVV"; }); //app init app.MapOpenApi(); ``` Makes both v1 and v2 documents available...

A workaround is to add a transformer: ``` services.AddOpenApi(opt => { opt.AddDocumentTransformer((document, _, _) => { foreach (var parameter in document.Paths.Values.SelectMany(v => v.Operations.Values).SelectMany(v => v.Parameters)) { if (parameter.Name == "api-version")...

While the proposed behaviour would be useful, one can also define a custom style for the relationship on the specification level: ``` -- specification relationship optional { line dotted }...

This works! I implemented the fix and published a new package version to our internal feeds, and now we can upgrade our odata projects to at least Swashbuckle 9. @AndreaCuneo...

This would be useful. I dislike having the AI assistant constantly bombarding me with suggestions, but very much like to flow of "press a button to get the next few...

This is still quite problematic, since we cannot upgrade many of our references due to this conflict between Versioning + OData + Swashbuckle

@commonsensesoftware I saw your update on #1140 - a huge thanks for your work and commitment is absolutely in order ❤️ I don't see a way to sponsor your open...

You absolutely deserve a whole box of donuts! Life happens to all of us

In a .net framework 4.8 app I can't seem to get around this without adding a bunch of binding redirects, which seems really iffy. So the choices for now seem...