I am getting this error in pactflow
# pactflow
s
I am getting this error in pactflow
m
sorry Sasank, that’s really hard to see. It looks like you have some error with the OAS rendering? does it render in https://editor.swagger.io/? That’s usually a good litmus test for valid OAS files
s
Matt I generated oas.yaml from postmantoopenapi and published to pactflow
m
Is it valid though?
Can you share at all?
s
message has been deleted
m
I’m sorry Sasank, we’ll need a wider view (not just visually, but information wise) to be able to help here. Do you have the OAS or a minimal version of an OAS that reproduces that problem?
s
Please Matt, Have a look and let me know your views
m
s
what is the alternative for it?
Is there any size limit for contract. json and oas.yaml fike
message has been deleted
Iam getting this error
m
You can’t have a request body for a GET. Once you change that to e.g. a
POST
there are other errors. I’d use editor.swagger.io as a guide to get it right. Once it properly renders and validates there, you can try uploading to PactFlow. PactFlow uses a similar UI library component (but doesn’t have the advanced validation/error messages of SwaggerHub).
s
I did validated and no errors displaying now but displaying No API definition provided after uploading to pactflow
Swagger spec file not displaying in pactflow of BDCT
Its working now
👍 1