Better Order of Methods

[fritterhoff]

If I generate a json from an openapi3.T the order of the Paths/Methods is pretty unusal (DELETE comes before GET). From my point of view this is caused due to the lexical order so Delete is serialized before Get and Post.

Is there maybe a way/... the serialize the spec in the "usual" order?

[ilteoood]

I think that it depends on how Go organize maps.

Btw, +1 here: it should be awesome to have an order.

[fritterhoff]

@ilteoood Wouldn't it be sufficient to manually serialize the PathItem struct in the correct order? From my pont of view the PathItem is the only point where it is really annoying.

kin-openapi/openapi3/path_item.go

Lines 32 to 34 in 8287d36

	func (pathItem *PathItem) MarshalJSON() ([]byte, error) {
	return jsoninfo.MarshalStrictStruct(pathItem)
	}

[fenollp]

cc #47 and also #37 also #98 (comment) and #241 This as well would benefit from a different (de)serialization: #485
also #513

Reworking de/serialization is on my TODO but I'm open to ideas / suggestions / PRs!