When using content extension .http with a path like demo/hello.http/pets/123 it will automatically try to project the field pets.123 from the return object.
This is not the use case I want, I want to be able to return a body and be able to access the path pets/123 (__ow_meta_path) to parse it and use it a path parameter in my web action.
Fixed by linked PR.
I wonder if we should remove all projections. I'm finding them increasingly frustrating to use.
Ha ! Finally you came around
I never love them and found them very confusing.
Don’t want to say “told you so”
oh you told me so!!!