Comments (5)
No, references should work wherever allowed by the spec. Can you share your files in a gist so I can debug?
from openapi-lint-vscode.
Afraid i can't share them - but i can try to recreate on an example - i'll see what i can do.
from openapi-lint-vscode.
Thanks. The extension uses the same libraries as boast
in the swagger2openapi
npm package. You could use that in verbose mode to see if there are any problems resolving your refs.
from openapi-lint-vscode.
Sorry - not used Gist before and saw an easy attach here option - hope this is ok.
petstore_no_components.yaml presents an error:
If you uncomment the parameters block in petstore_no_components.yaml and switch the commented lines in the refs to use the local parameters all errors go, indicating the schemas references in the external file are resolving fine.
from openapi-lint-vscode.
I'll admit this is a little confusing in the current version. The message means the reference cannot be resolved as an internal reference. The command you need to use is "OpenAPI Resolve and Lint" if your API definition is made of multiple parts. I'll probably soon release a new version where this is the default behaviour anyway.
from openapi-lint-vscode.
Related Issues (20)
- Unable to get intellisense unless rename to oas2.yaml HOT 3
- Doesn't work offline HOT 6
- Swagger 2.0 in openapi.yml validates against the incorrect spec HOT 1
- Enhancement: Validation & linting commands should integrate with the VSCode "problems" panel HOT 1
- Configurable names for OAS v3/v2 intellisense for files HOT 2
- Problem: String is not a URI: [UriError]: Scheme is missing HOT 3
- Not working with asyncapi file HOT 2
- Linting/Validation does not default to "resolve" HOT 4
- references that contain ~0 or ~1 tokens fail lint
- Extension causes high cpu load HOT 4
- On validate/lint errors the plugin crashes HOT 2
- Release version 1.3.0
- better error output in case the yaml could not be parsed
- Parsing and linting inline OpenAPI documentation HOT 3
- Remove or replace "*" in activationEvents
- Linter crashes with missing range
- multiple openapi.yaml files show errors HOT 9
- Reference path containing spaces can not be opened HOT 9
- OpenApi 3.x validation error when "servers" object is present HOT 16
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from openapi-lint-vscode.