Postman v2.1.0 to Hoppscotch: Environment Variable Scope Preservation

Postman v2.1.0 to Hoppscotch: Environment Variable Scope Preservation

The goal is to import a Postman collection that references an environment file and have all variables available in Hoppscotch with their original scopes (global, environment) and structural integrity.

Current constraints include the fact that Hoppscotch flattens nested objects in imported environments, discards scope information, and does not automatically load environment files during collection import. This leads to missing or incorrectly scoped variables when requests are executed.

Uncertainties remain about whether future releases will address these gaps and what the best workflow is to maintain variable fidelity.

• When a Postman environment contains nested objects, does Hoppscotch preserve the nested structure upon import?
• How does Hoppscotch treat variable scopes (global vs. environment) during the import of a Postman collection?
• Are there documented workarounds or configuration options to retain original scopes and nested structures when importing Postman v2.1.0 collections into Hoppscotch?