EnableNavigationPropertyPath per parameter for OoasUtil

[DominicRoth]

Hello,

with every new release we have to put the Value vor EnableNavigationPropertyPath hardcoded to false. Is there a way to include it as an parameter for a future release? We have an automatic call per pipeline, so we cannot use the OoasGUI-Tool.

Regards,
Dominic

[irvinesunday]

@DominicRoth we currently pass the parameters as below:

OpenApiConvertSettings settings = new() 
{
    EnableNavigationPropertyPath = false
};

OpenApiDocument document = EdmModel.ConvertToOpenApi(Settings);

can you provide further details on a different approach that you have in mind?