Directories
¶
| Path | Synopsis |
|---|---|
|
Package bug1026 probes whether a custom vendor extension (x-logo) can be declared in the swagger:meta block — the #1026 "x-logo feature" request is satisfied by generic InfoExtensions support rather than a dedicated knob.
|
Package bug1026 probes whether a custom vendor extension (x-logo) can be declared in the swagger:meta block — the #1026 "x-logo feature" request is satisfied by generic InfoExtensions support rather than a dedicated knob. |
|
Package r1092 probes a swagger:meta with colon-bearing prose lines (#1092).
|
Package r1092 probes a swagger:meta with colon-bearing prose lines (#1092). |
|
1109
|
|
|
bodyref
Package bodyref reproduces go-swagger issue #1109 using casualjim's recommended "200: body:order" form, which references a model as the response body.
|
Package bodyref reproduces go-swagger issue #1109 using casualjim's recommended "200: body:order" form, which references a model as the response body. |
|
responseref
Package responseref reproduces go-swagger issue #1109 using the OP's exact "200: order" form, where "order" names a model (not a named response object).
|
Package responseref reproduces go-swagger issue #1109 using the OP's exact "200: order" form, where "order" names a model (not a named response object). |
|
Package bug1121 probes whether tag descriptions (the OAI root-level tags section, with description / externalDocs per tag) can be declared from code.
|
Package bug1121 probes whether tag descriptions (the OAI root-level tags section, with description / externalDocs per tag) can be declared from code. |
|
The Documentation of project is described here.
|
The Documentation of project is described here. |
|
josev2
Package jose lives in a directory ("josev2") whose name does NOT match the package name ("jose") — like gopkg.in/square/go-jose.v2 in the issue.
|
Package jose lives in a directory ("josev2") whose name does NOT match the package name ("jose") — like gopkg.in/square/go-jose.v2 in the issue. |
|
Package bug1595 reproduces go-swagger#1595: a swagger:operation written in a /* */ block comment must scan like its // equivalent.
|
Package bug1595 reproduces go-swagger#1595: a swagger:operation written in a /* */ block comment must scan like its // equivalent. |
|
Package bug1726 covers go-swagger#1726: markdown-style bullet lists (`* item`, `+ item`) must be identified as lists exactly like the YAML-style dash form (`- item`), everywhere the annotation language recognises a list.
|
Package bug1726 covers go-swagger#1726: markdown-style bullet lists (`* item`, `+ item`) must be identified as lists exactly like the YAML-style dash form (`- item`), everywhere the annotation language recognises a list. |
|
api
Package api holds a parameters struct in a DIFFERENT package from the route that references it (go-swagger#1742).
|
Package api holds a parameters struct in a DIFFERENT package from the route that references it (go-swagger#1742). |
|
paramsx
Package paramsx holds a parameters struct used by a swagger:operation in another package (go-swagger#1955).
|
Package paramsx holds a parameters struct used by a swagger:operation in another package (go-swagger#1955). |
|
api
Package api holds a body type referenced from another package (go-swagger#2002).
|
Package api holds a body type referenced from another package (go-swagger#2002). |
|
Documentation for API.
|
Documentation for API. |
|
Package bug2294 is the witness for go-swagger#2294: a global Security requirement that combines TWO schemes with AND logic — both must be satisfied.
|
Package bug2294 is the witness for go-swagger#2294: a global Security requirement that combines TWO schemes with AND logic — both must be satisfied. |
|
Package bug2403 is the witness for go-swagger#2403: a global Security requirement in swagger:meta written as a YAML sequence.
|
Package bug2403 is the witness for go-swagger#2403: a global Security requirement in swagger:meta written as a YAML sequence. |
|
2417
|
|
|
2540
|
|
|
foo
Package docs SwagTest
|
Package docs SwagTest |
|
sub
Package sub provides an imported numeric-ish type.
|
Package sub provides an imported numeric-ish type. |
|
Package bug2637 reproduces go-swagger issue #2637 ("Cyclic type definition for defined types using the same name"): a local type defined from a same-named type in another package collides on the short key and the definition gets a SELF-$ref alongside its properties — an invalid, self- cyclic definition that hangs downstream codegen.
|
Package bug2637 reproduces go-swagger issue #2637 ("Cyclic type definition for defined types using the same name"): a local type defined from a same-named type in another package collides on the short key and the definition gets a SELF-$ref alongside its properties — an invalid, self- cyclic definition that hangs downstream codegen. |
|
Package bug2638 reproduces go-swagger issue #2638 ("Improper handling of multiple variables on one line"): a struct field group declaring several names on one line (`R, G, B, A uint8`) must emit one property per name, instead of a single mislabeled property.
|
Package bug2638 reproduces go-swagger issue #2638 ("Improper handling of multiple variables on one line"): a struct field group declaring several names on one line (`R, G, B, A uint8`) must emit one property per name, instead of a single mislabeled property. |
|
Package bug2651 reproduces go-swagger issue #2651: an operation that mixes inline `swagger:operation` parameters with a `swagger:parameters`-bound struct mis-binds — the bound body schema is attached to the inline path parameter instead of becoming its own body parameter.
|
Package bug2651 reproduces go-swagger issue #2651: an operation that mixes inline `swagger:operation` parameters with a `swagger:parameters`-bound struct mis-binds — the bound body schema is attached to the inline path parameter instead of becoming its own body parameter. |
|
Package bug2655 reproduces go-swagger issue #2655 (tag metadata ignored): a tag list in swagger:meta must populate the top-level tags section (with per-tag descriptions, externalDocs and vendor extensions), not be swallowed into info.description.
|
Package bug2655 reproduces go-swagger issue #2655 (tag metadata ignored): a tag list in swagger:meta must populate the top-level tags section (with per-tag descriptions, externalDocs and vendor extensions), not be swallowed into info.description. |
|
Package bug2701 reproduces go-swagger issue #2701 ("In path parameter for an embedded struct is ignored and thus defaults to query"): an `in: path` annotation on an EMBEDDED struct field in a swagger:parameters type is ignored — the promoted fields default to `in: query`.
|
Package bug2701 reproduces go-swagger issue #2701 ("In path parameter for an embedded struct is ignored and thus defaults to query"): an `in: path` annotation on an EMBEDDED struct field in a swagger:parameters type is ignored — the promoted fields default to `in: query`. |
|
Package bug2783 reproduces go-swagger issue #2783 ("Models get mixed when using structs from several packages"): two packages each declare a swagger:model named Test.
|
Package bug2783 reproduces go-swagger issue #2783 ("Models get mixed when using structs from several packages"): two packages each declare a swagger:model named Test. |
|
Package main An example API
|
Package main An example API |
|
Package bug2804 reproduces go-swagger issue #2804 ("Should swagger:parameters support map[string][]string?"): a map-typed swagger:parameters field crashes the scan with a nil-pointer dereference in parameterBuilder.buildFromField (Schema.Typed on a nil schema), rather than producing a parameter or a diagnostic.
|
Package bug2804 reproduces go-swagger issue #2804 ("Should swagger:parameters support map[string][]string?"): a map-typed swagger:parameters field crashes the scan with a nil-pointer dereference in parameterBuilder.buildFromField (Schema.Typed on a nil schema), rather than producing a parameter or a diagnostic. |
|
Package bug2872 reproduces go-swagger issue #2872 ("ExternalDocs are not generating the 2.0 spec on swagger:meta"): an ExternalDocs block in swagger:meta is not emitted (KwExternalDocs exists in the grammar but is not wired into the meta/info builder).
|
Package bug2872 reproduces go-swagger issue #2872 ("ExternalDocs are not generating the 2.0 spec on swagger:meta"): an ExternalDocs block in swagger:meta is not emitted (KwExternalDocs exists in the grammar but is not wired into the meta/info builder). |
|
2907
|
|
|
Package bug2909 reproduces go-swagger issue #2909 ("Regular cannot generate swagger automatically"): a route path with an inline regex segment (gorilla/chi style, e.g.
|
Package bug2909 reproduces go-swagger issue #2909 ("Regular cannot generate swagger automatically"): a route path with an inline regex segment (gorilla/chi style, e.g. |
|
Package bug2922 reproduces go-swagger issue #2922 ("enum description: superfluous name&values"): the enum const-name mapping (e.g.
|
Package bug2922 reproduces go-swagger issue #2922 ("enum description: superfluous name&values"): the enum const-name mapping (e.g. |
|
Package bug2942 reproduces go-swagger issue #2942 ("how can i generate spec with a simple string response").
|
Package bug2942 reproduces go-swagger issue #2942 ("how can i generate spec with a simple string response"). |
|
Package bug2985 reproduces go-swagger issue #2985 ("Need minAttributes and maxAttributes in the swagger:model annotation"): code-to-spec lacks minProperties / maxProperties support that spec-to-code already has.
|
Package bug2985 reproduces go-swagger issue #2985 ("Need minAttributes and maxAttributes in the swagger:model annotation"): code-to-spec lacks minProperties / maxProperties support that spec-to-code already has. |
|
Package bug3005 covers go-swagger issue #3005 ("additionalProperties are lost when generating spec from code"): a model wants named properties AND additionalProperties.
|
Package bug3005 covers go-swagger issue #3005 ("additionalProperties are lost when generating spec from code"): a model wants named properties AND additionalProperties. |
|
Package bug3013 reproduces go-swagger issue #3013 ("How to set an example value for array/string response type?"): an `example:` annotation on a response whose body is a top-level array type is dropped.
|
Package bug3013 reproduces go-swagger issue #3013 ("How to set an example value for array/string response type?"): an `example:` annotation on a response whose body is a top-level array type is dropped. |
|
Package bug3035 reproduces go-swagger issue #3035 ("Example spec for swagger:response does not produce example output"): a swagger:response whose body is an anonymous inline struct used to emit only the response description, with no schema at all — so field-level Example/Required and property descriptions were lost.
|
Package bug3035 reproduces go-swagger issue #3035 ("Example spec for swagger:response does not produce example output"): a swagger:response whose body is an anonymous inline struct used to emit only the response description, with no schema at all — so field-level Example/Required and property descriptions were lost. |
|
Package bug3069 demonstrates the resolution to go-swagger issue #3069 ("Is there a way to change the representation of one parameter of the request object?").
|
Package bug3069 demonstrates the resolution to go-swagger issue #3069 ("Is there a way to change the representation of one parameter of the request object?"). |
|
Package bug3100 reproduces go-swagger issue #3100: a parameter declared with `in: formData` inside an inline `swagger:route` annotation lost its `in` field in the generated spec (the scanner only recognised `form`), so the parameter rendered with name/type/description but no `in`.
|
Package bug3100 reproduces go-swagger issue #3100: a parameter declared with `in: formData` inside an inline `swagger:route` annotation lost its `in` field in the generated spec (the scanner only recognised `form`), so the parameter rendered with name/type/description but no `in`. |
|
3107
|
|
|
api
Package api carries the route whose response references the model in a sibling package, exercising cross-package type resolution for issue #3107.
|
Package api carries the route whose response references the model in a sibling package, exercising cross-package type resolution for issue #3107. |
|
model
Package model reproduces go-swagger issue #3107 ("No struct definition in swagger generate"): under `generate spec -m`, MyStruct was emitted as an empty definition carrying only `x-go-package`, with its fields dropped.
|
Package model reproduces go-swagger issue #3107 ("No struct definition in swagger generate"): under `generate spec -m`, MyStruct was emitted as an empty definition carrying only `x-go-package`, with its fields dropped. |
|
3125
|
|
|
Package bug3138 reproduces go-swagger issue #3138 ("How To mark a field as deprecated?").
|
Package bug3138 reproduces go-swagger issue #3138 ("How To mark a field as deprecated?"). |
|
Package bug3213 reproduces go-swagger issue #3213 ("Consider TypeSpec comments"): annotations and doc comments attached to an individual TypeSpec inside a grouped `type ( ...
|
Package bug3213 reproduces go-swagger issue #3213 ("Consider TypeSpec comments"): annotations and doc comments attached to an individual TypeSpec inside a grouped `type ( ... |
|
Package bug3214 reproduces go-swagger issue #3214: a struct field that references a named primitive type whose doc comment carries both prose and an inline `enum:` annotation.
|
Package bug3214 reproduces go-swagger issue #3214: a struct field that references a named primitive type whose doc comment carries both prose and an inline `enum:` annotation. |
|
maps
Package maps stands in for an external library (googlemaps.github.io/maps) whose exported struct carries a custom-typed field.
|
Package maps stands in for an external library (googlemaps.github.io/maps) whose exported struct carries a custom-typed field. |
|
A Bug API
|
A Bug API |
|
Package bug958 reproduces go-swagger issue #958 ("how to specify sample values in user structs"): a field-level `default:` / `example:` was carried for a plain builtin field but dropped when the field used a named (defined) type such as `type SpecificType string`.
|
Package bug958 reproduces go-swagger issue #958 ("how to specify sample values in user structs"): a field-level `default:` / `example:` was carried for a plain builtin field but dropped when the field used a named (defined) type such as `type SpecificType string`. |
Click to show internal directories.
Click to hide internal directories.