Andrew Tatomyr
Andrew Tatomyr
Thanks, @matthieuLepetit! The main thing here is to test if it doesn’t break anything for us. I'll be able to do that a bit later this week (I hope).
@garrett-whitehorn-cengage this has been fixed in v2. You may start using the pre-release `next` version before we go launch the stable version. I'm currently preparing the migration guide, but in...
Resolved in v2.
Have you tried using the `--remove-unused-components` [option](https://redocly.com/docs/cli/decorators/remove-unused-components#remove-unused-components)?
Ah, so you want to bundle your files, preserve the existing components, and not add the new ones? Then it's more of an enhancement rather than a bug. I'm not...
Hi @gnvk. I don't see an easy workaround for your problem. To achieve that, we'd need to change the current behaviour of Redocly CLI which might impact existing users. Have...
@gnvk I see. Then the only workaround I can suggest is running a decorator on the stock.yaml to remove the needless `stock-` prefixes in components and refs. It seems to...
It should adjust to the spec version in the document you're linting, as the built-in rules are spec-aware. If you're interested in following specifications, you might find the built-in [spec...
@uncaught there's one more possible option you can try to work around that: writing a [custom decorator](https://redocly.com/docs/cli/custom-plugins/custom-decorators/) to remove duplicated components in the joined file. You may start with something...
Thanks @NeelChotai! I'll review your PR once I have time.