thegagne

I also ran into this -- found out when I tried to use `@opExample` and it wanted the Lifecycle.Read version of the object on an update. Here's a playground example...

> in the context of AEPs, we dont recommend async. I'd love to hear more about this and it might be good to have some actual guidance for this on...

The options: - query param - header - path (custom method) - body At the moment I lean towards it being in the body, as `dry_run: true` in both the...

Bump! Can we get some more examples on this? I'm new to CEL, and ChatGPT it's suggesting things like this: ``` # property == whatever GET /properties?filter=property%20%3D%3D%20%22whatever%22 # "foo" in...

I think I agree with the above, but what alternative is there? Many APIs have very basic filtering needs that could be defined by simple query strings that match model...

I think we can make this easier on developers while still keeping a consistent standard by supporting two filtering options: **1. Basic Filtering** The simplest approach: normal query params that...

I do think improving the doc with some simple examples could be helpful, but it would not block the release of 2025.

The issue with the `/:custom-method` approach is it might look too much like path-to-regexp style parameters. See https://github.com/pillarjs/path-to-regexp And for example: https://zuplo.com/docs/articles/routing I'm not certain this overlap is a problem,...

Do we need the operations to be _per field_? For example, you might want `RelOp` for `create_time` but not for `description`.

Sorry I think the confusion came from https://aep.dev/122/#fields-representing-a-resources-parent - this is proto specific but that page does not distinguish between OAS and proto.