We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
For API mocking purposes and to avoid creating demo or trial company i tried to run Accounting openapi in Prism but with no luck.
Command prism mock Xero-OpenAPI/xero_accounting.yaml runs a mock server
prism mock Xero-OpenAPI/xero_accounting.yaml
Got fatal Cannot set property $ref of #<Object> which has only a getter error
fatal Cannot set property $ref of #<Object> which has only a getter
So i tried to open openapi file in stsoplight.io to see possible errors in specification and found a lot of errors and warnings:
Typical errors are:
Removing quotes around object in example section fixes this error
A lot of similar errors that appear after fixing examples blocks
So mostly i found out - that problem is with quotes, but after fixing it - new errors happen.
I suppose after fixing all errors - it should run correctly with Prism.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
For API mocking purposes and to avoid creating demo or trial company i tried to run Accounting openapi in Prism but with no luck.
Expected Behavior
Command
prism mock Xero-OpenAPI/xero_accounting.yaml
runs a mock serverCurrent Behavior
Got
fatal Cannot set property $ref of #<Object> which has only a getter
errorPossible Solution
So i tried to open openapi file in stsoplight.io to see possible errors in specification and found a lot of errors and warnings:
Typical errors are:
Removing quotes around object in example section fixes this error
A lot of similar errors that appear after fixing examples blocks
So mostly i found out - that problem is with quotes, but after fixing it - new errors happen.
I suppose after fixing all errors - it should run correctly with Prism.
The text was updated successfully, but these errors were encountered: