if included file is renamed or moved to another directory, Specmatic backward-compatibility-check interest this non-breaking changes as breaking changes

[mickle-ak]

Specmatic's "backward-compatibility-check" does not interpret some non-breaking changes as non-breaking – if included file is renamed or moved to another directory:

In the test project SpecmaticBackwardCompatibilityCheck I rename the included file “includedAsOpenApiDocument.yaml” into (for example) “includedOpenApiDocument.yaml“ and start backward-compatibility-check.

java -jar specmatic.jar backward-compatibility-check

Return code: 1
Output:

Specmatic Version: 2.6.0
Checking backward compatibility of the following specs:
  - Specs that have changed: 
    1. D:\my\SpecmaticBackwardCompatibilityCheck\.\includedOpenApiDocument.yaml
    2. D:\my\SpecmaticBackwardCompatibilityCheck\.\root.yaml
  - Specs referring to the changed specs: 
    1. .\includedOpenApiDocument.yaml
    2. .\root.yaml
--------------------
1. Running the check for D:\my\SpecmaticBackwardCompatibilityCheck\.\includedOpenApiDocument.yaml:
read(...) must not be null

This change is not breakable, the OAS is only reorganized but not changed at all.

I think, this problem is very closed to this one (#1643) – Probably should Specmatic validate only whole AOS, not as separated files.

[harikrishnan83]

@mickle-ak Thanks again for the detailed bug report. Yes, it initial glance looks quite related to #1643 . I will take a look and get back in this.