Early start to supporting sourcemaps.

[kevinswiber]

A work in progress towards postmanlabs/openapi-to-postman#220.

Signed-off-by: Kevin Swiber [email protected]

[kevinswiber]

Unfortunately, IDs set to requests on items don't seem to actually propagate via the Postman API, so it seems to be the only artifact left that comes back as "modified". Any thoughts here?

[abhijitkane]

@kevinswiber Could you expand your last comment? My understanding is:

1. A source map is a map from an OpenAPI operation to a Postman request ID
2. Source maps are generated during conversion from OAS to collection
3. Source maps are accepted as optional input during conversion - these will be used to add the same request IDs in the generated collection.

Is the blocker that even keeping the IDs the same will cause the collection feed to show a diff for all requests?

[kevinswiber]

@abhijitkane When updating a collection via the Postman API, if IDs for folders and responses are set, they persist. This means we can get more granular updates for these in Postman Version Control. However, for requests, the IDs do not persist on a collection update. The request IDs are all regenerated, despite being set, and Postman Version Control marks them all as new while all previous ones are removed. This makes it really difficult to review modifications between transpile events.