Common path extraction in the align command is not working correctly

[TharaniDJ]

Area

None

Description

No response

Steps to Reproduce

This is the Openapi spec I used

https://github.com/docusign/OpenAPI-Specifications/blob/master/admin.rest.swagger-v2.1.json

After running these 2 commands

bal openapi flatten -i docs/spec/openapi.yaml -o docs/spec
bal openapi align -i docs/spec/flattened_openapi.yaml -o docs/spec

I tried to generate a connector using the above file, then I encountered this issue

OpenAPI definition has errors:
paths. Resource .1/organizations/{organizationId}/accounts/{accountId}/dsgroups should start with /
paths. Resource .1/organizations/{organizationId}/accounts/{accountId}/dsgroups/{dsGroupId} should start with /
paths. Resource .1/organizations/{organizationId}/accounts/{accountId}/dsgroups/{dsGroupId}/users should start with /
paths. Resource .1/organizations/{organizationId}/accounts/{accountId}/products/permission_profiles should start with /
paths. Resource .1/organizations/{organizationId}/accounts/{accountId}/products/users/{userId}/permission_profiles should start with /
paths. Resource .1/organizations/{organizationId}/accounts/{accountId}/users should start with /
paths. Resource .1/organizations/{organizationId}/users/dsprofile should start with /
paths. Resource .1/organizations/{organizationId}/users/{userId}/dsprofile should start with /
paths. Resource .1/organizations/{organizationId}/accounts/{accountId}/products/users should start with /
paths. Resource .1/organizations/{organizationId}/accounts/{accountId}/products/permission_profiles/users should start with /

Version

v2.1

Environment Details (with versions)

No response

[TharmiganK]

@TharaniDJ The issue is with the basepath(common path) extraction logic in bal openapi align command.

Use this as a workaround:

$ bal openapi align -i flattened_openapi.json --exclude basepath

[github-actions]

This issue is NOT closed with a proper Reason/ label. Make sure to add proper reason label before closing. Please add or leave a comment with the proper reason label now.

      - Reason/EngineeringMistake - The issue occurred due to a mistake made in the past.
      - Reason/Regression - The issue has introduced a regression.
      - Reason/MultipleComponentInteraction - Issue occured due to interactions in multiple components.
      - Reason/Complex - Issue occurred due to complex scenario.
      - Reason/Invalid - Issue is invalid.
      - Reason/Other - None of the above cases.