Comments (2)
I didn't understand your remark about why per-api definitions wouldn't work but there are a few different approaches you could try:
- write a separate config file for each of the different validations you want to use, and then supply it with
--config
when you run thelint
command (it sounds like you are doing it this way already, and I think it's a good approach) - use custom plugin configuration to define easily reusable rulesets
Write an external function to work out which ruleset to use, and then use redocly to do the linting. Let us know how you get on?
from redocly-cli.
Hello, sorry for the late response... 😃
What I want to achieve is:
- Depending of a specific value INSIDE the json file (info.x-state) (draft,development,stable,deprecated) I want to run different validations.
- In my validation script I read the value from the file and use different config files
- In the Visual Studio Code plugin there is a single redocly.yaml file with a single definition, so I cannot run any script...
- Built-in validations do not support adding a where clause, so I cannot change them dynamically (fixing this could be a solution)
What I was suggesting is to allow some plugin extension to define a list of extensions by running some js code. This way I could use a single initial config that would run different extends based on the file.
Thanks!
from redocly-cli.
Related Issues (20)
- Support internalFlagProperty as a list for remove-x-internal decorator HOT 2
- Update syntax for decorators to support markdown as well as file paths
- Support for operations that respond with `1xx` status codes HOT 5
- Incorrect command to preview local docs changes in contributing.md HOT 3
- Review guide for replacing servers list HOT 1
- redocly lint format html or markdown HOT 5
- better error handling when $ref references an external file in asyncapi HOT 7
- asyncapi lint support custom rules HOT 8
- Can't resolve remote $ref with query parameter HOT 3
- OAS 3.1 - arbitrary schema keywords are classified as lint errors HOT 3
- Missing const typing support HOT 2
- bug: inconsistent types for OAS3_1 schemas HOT 1
- Support better means to set environment variables HOT 2
- dependentRequired is valid json schema but does not pass linting and prevents component from being available in UI. HOT 3
- Api HOT 2
- Add the `--ext` parameter to the `split` command HOT 1
- Running out of CPU inside of containers HOT 2
- join fails on commonly referenced components
- Redocly removing string for enums if there's non-numbers mixed in HOT 3
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 redocly-cli.