Remove checks for unexpected reference depth#1392
Conversation
In my opinion, this check doesn't seem to be providing much value, and we've got a few folks requesting this be disabled. Instead of gating this behind a feature flag, we'll just remove it. Closes #1348.
|
Requires we actually inspect what's at that path and reference that |
|
@jamietanna Any news on this? I'm still encountering the error in question. |
|
@jhawrefvem please can you raise an issue (https://github.com/oapi-codegen/oapi-codegen/blob/main/CONTRIBUTING.md#raising-a-bug) for this? This may now be closed by #1689 and some follow up changes |
|
When to merge this to main branch? |
|
If you're still seeing issues with this, please raise an issue, as this may not be an issue any more due to other changes we've made over time @moemoequte |
|
@jamietanna I put the problem I met in this pull request #1950 |
|
Thank you for contributing, and I'm very sorry for taking so long to get to this PR. At this point, the code has changed so much that it's no longer relevant because reference depth handling has evolved significantly and this has likely been superseded by PR #1689 and related work. |
3 participants
unexpected reference depthCloses #1348.