inso lint does not load custom .spectral.yml when linting API specs using --exportFile flag

[karivatj]

Expected Behavior

The expected behavior is that the Inso CLI should load the custom ruleset from .spectral.yaml, just as it does when linting an API spec directly. When running inso lint spec somespec.yaml, it is indicated in the console that the Spectral YAML is being loaded. However, this does not occur when linting with inso lint spec --exportFile some-exportfile.json "Some API Spec identifier here

Actual Behavior

The Inso CLI does not use the .spectral.yaml file in the current working directory when the --exportFile flag is used to define an Insomnia v4 export file (Design Document).

Reproduction Steps

1. Export a design document containing an API specification.
2. Create a .spectral.yml file and add custom rulesets.
3. Lint the API spec within the export file using inso lint spec --exportFile export.json "API Spec identifier".
4. Check the console to see if the Spectral YAML file is being loaded.

Is there an existing issue for this?

• I have searched the issue tracker for this problem.

Additional Information

No response

Insomnia Version

9.3.3 (inso-cli)

What operating system are you using?

Windows

Operating System Version

Windows 01

Installation method

Download from insomnia.rest

Last Known Working Insomnia version

N/A