nickcorby

Hi @jeremyfiel thanks for taking the time to look at this and provide some feedback. I know what I've written isn't valid OpenAPI on its own, but with the `bundle`...

Hi @tatomyr I'm not sure if this is related to the initial issue - I'm restructuring my `base.yaml` file to try and make everything more OpenAPI compliant & am consulting...

@tatomyr thanks for clarifying - I guess the errors just come with the "filter-per-operation" option not being semantically correct. Nice suggestion with the `split` command (thank you again). I tried...

@tatomyr no error from the per-path references or the split, I was just hoping for a per-operation split! I'm not declaring my `schemas` property explicitly anymore which is working as...

@AlbinaBlazhko17 I'm also experiencing this - on `2.7.0` it looks like it's removing all of the components that **are** being used, and is leaving the components that **aren't** (the inverse...

@AlbinaBlazhko17 I think this might be the cause of the issue. My base.yaml file is structured like so: ``` openapi: "3.0.2" info: title: "Gateway" version: "v1" description: "Publicly accessible API"...

@AlbinaBlazhko17 thanks for getting back to me. I understand this doesn’t follow OpenAPI specification, however I didn’t think this would be an issue, especially as this structure does work with...

@AlbinaBlazhko17 removing `components/schemas` from the base file seems to be working. Thank you for the suggestion! @ethanmdavidson I reported a bug a few weeks ago where the `bundle` function wasn't...