Use relative specification file path not working as expected

[Krimsar]

Describe the bug

I select "use relative specification file path" and only leave the file name of my specification.yaml in the "will combine with:" edit field. When I click finish and inspect the generated files, the "Endpoint" setting in the "ConnectedService.json" contains the full path to the specification. When you then run the wizard again through "Update Unchase OpenAPI (Swagger) Connected Service...", the "will combine with:" edit field now contains the full path as well.

Assemblies affected

Unchase OpenAPI (Swagger) Connected Service 1.5.8

Expected result

I would expect the full path to be constructed at run-time using the project directory and the path to the specification file, relative to it, so that the project can be used independently from it's location (and shared between devs).

Actual result

The full path to the specification.yaml file is saved inside "ConnectedService.json" and as soon as you rename the solution folder, or move the solution folder to a different location, the next time you start the wizard, it fails.

[Krimsar]

Thanks a lot! I can confirm it's working as expected now :)