Troy Milán

A previous ticket regarding circular references: https://github.com/stoplightio/prism/issues/1456

Hey @hieucd04 - Sorry this one got lost. Your use case makes sense and our documentation does give the impression that [unimplemented ops will be mocked](https://meta.stoplight.io/docs/prism/ZG9jOjk3-validation-proxy#unimplemented-operations-will-be-mocked), so it stands to...

Removing points to re-groom and discuss with team.

Consider: - Option 1, w/o cache: 8 - If performance is bad, add cache: 5

Todo: - Improve error messaging - Create CLI parameter for expanding the node limit

Hey team! Please [add your planning poker estimate](https://app.zenhub.com/workspaces/-Team-Tacocat-5eb9bc4a1fddfe30b94f78b1/issues/stoplightio/prism/2033?planning-poker) with Zenhub @chohmann @EdVinyard @daniel-white @brendarearden

Todo: Let's add an additionalProperties override as a CLI parameter so that it doesn't have to be defined in every schema.

Hey team! Please [add your planning poker estimate](https://app.zenhub.com/workspaces/-Team-Tacocat-5eb9bc4a1fddfe30b94f78b1/issues/stoplightio/prism/2046?planning-poker) with Zenhub @chohmann @EdVinyard @daniel-white @brendarearden

While the original example lacked the necessary (for OAS3.0) `minimum` and `maximum` values, I can confirm that the problem persists even with these values. [prism2082.yaml.txt](https://github.com/stoplightio/prism/files/11125351/prism2082.yaml.txt)

I don't think we're going to be able to address this functionality any time soon, so I'm going to close this ticket and update our documentation with the suggestions mentioned...