Roman Hotsiy

> For description and summary - take it from first document Yes, I would also show a warning if there are different values and they mismatch. > For servers -...

I'm not sure about those above. I think what we should do is to sort top-level yaml keys before saving the output. I think we should do it always (not...

One of the other advantages of not going deep in nested visitors is performance. @aviskase could you please describe your use case?

@aviskase sorry for the radio silence 🙉. I believe your use case is valid. But I don't have a good solution yet. Same schema may be referenced from multiple places...

Actually, we discussed it a little bit more. @jeremyfiel can you use a plugin? We have a mechanism for types tree extension so you can modify/extend it from the plugin....

@jeremyfiel we don't support wildcards in ignore files unfortunately. This is a nice idea to consider. I think we need to support a way to append to the ignore file....

Follow the [custom plugins docs](https://redocly.com/docs/cli/resources/custom-rules/#custom-plugins) and use the following types extension: https://redocly.com/docs/cli/resources/custom-rules/#type-extensions-in-plugins ``` module.exports = { id: 'my-plugin-id', typeExtension: { oas3(types) { // modify types here return { ...types, Schema:...

You should not use all ruleset. This is intended for internal use for benchmarks/etc. It may have conflicting rules. We'll have to fix it in the docs.

cc @skadinna

@adamaltman I agree.