-
Notifications
You must be signed in to change notification settings - Fork 126
New issue
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
Add some type of plugin to allow dynamic definition of extensions or config files #1551
Comments
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 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? |
Hello, sorry for the late response... 😃
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! |
I have a use case where I run different validations on the files depending on their "state": draft, development, stable or deprecated.
I have 4 different config files for each, but I would like a plugin with a function that would receive the root element and based on the information I decide I can return an extends line or something like that.
I cannot use per-api definitions because I would have to sync the main redocly with the actual state of the files...
Do you have a way to do this?
Thanks! The tool is great and I intend to use it extensively.
The text was updated successfully, but these errors were encountered: