Zanie Blue
Zanie Blue
Thanks for the MRE! I believe this may be addressed by #6948 — can you try to reproduce with that branch?
I'll be investigating a fix for this.
Hi. Thanks for this request! We'll need to think about this a bit. Can you provide of some example routes with existing and preferred operation identifiers? It'd also be great...
Thanks! We'll need to gather some feedback from some relevant stakeholders before we can add this to our backlog. Are you interested in contributing this if we're willing to accept...
@abrookins let's try to get this issue out of triage. @darin-reify I don't see any reason for us not to do this, we'll just need to decide on a consistent...
@tpdorsey that seems okay with me, at least there won't be references to features that you _can't_ use yet. We could pin to each minor version (e.g. `2.5`, `2.6`) instead...
We reset the database using a test fixture so this isn't going to work with just the API URL, we'll need access to the API's database as well.
We have addressed this with different backwards compatibility integration tests so I'm dropping the priority of this.
It'd be great to run the full test suite instead of a small set of integration tests, I do not have qualms with it lingering here as a future goal....
Thanks for the report! This is definitely incorrect behavior. I believe this is because `caller_async` does not have handling for wrapped functions, but I'm not sure. We'll need to investigate.