Importing a TypeSpec file

TypeSpec (Microsoft) describes an API in a dedicated language, then compiles it to OpenAPI. Restorm follows that same route.

Importing

File ▸ Import (Ctrl+I) then a .tsp file from disk.

Restorm compiles the file to OpenAPI 3.x with its embedded TypeSpec compiler, then hands the result to the OpenAPI import. You therefore get exactly the same rich tree: folders per tag, typed requests, documentation, pre-wired security.

Trust model

The .tsp content is copied into an isolated temporary folder, into which Restorm mounts its own dependencies. The consequence: a tspconfig.yaml or a node_modules sitting next to your source file are never consulted. Compilation therefore cannot run arbitrary code coming from your own tree.

Limitations

• Local file only. Pasting and importing by URL are refused with an explicit message.
• Single-file specification. Relative imports to neighbouring .tsp files are not resolved — a direct consequence of the isolation above. Compile to OpenAPI yourself and import the result if your model is split across several files.