Udit Vasu

@sastava007 every language has different options to configure a proxy (e.g, `--proxy` in curl). This feature request is about setting that proxy configuration (for different languages/code generators) if the given...

@csk1827 Sure 👍

deferring because the same issue is present in other `Property`.

If the JSDoc is present in the proxy config source then probably the hosted document is outdated.

@XVincentX the definitely typed was a community contribution and the bundled types are auto-generated using the existing JSDoc. We didn't want the overhead of updating two sources to it's best...

@XVincentX First of all, I really appreciate your hard work for maintaining the definitely typed definitions. Now, `toObjectResolved` is missing because it's a private method and `PropertyBaseDefinition` is available [here](https://github.com/postmanlabs/postman-collection/blob/develop/types/index.d.ts#L1153)....

Looks like bundled types are affecting a lot of your use cases. Since we don't have enough bandwidth to fix the auto-generated types at the moment... we'll just remove the...

As mentioned in https://github.com/postmanlabs/postman-collection/issues/602#issuecomment-740129552, released `v3.6.9` without specifying the bundled declarations in the package.json (removed `types` property).

We have plans to introduce types in variables (this library already supports a few types) but without that, the existing interpolation is a simple string replacement.

Agree that this is an unexpected behavior but I would rather like to bail out early with an error than executing an invalid (with missing items) run.