Mike
Mike
@shankie-san @jedrichards Thanks for the feedback. Yeah a flag to opt into it sounds good. I'll reopen the ticket. I'd probably want to keep the current default to be backwards...
Are you getting any type of stack trace or just the not-so-helpful details you mentioned? Would you be able to share any of the document or is it private? Also...
@Sunjammer thanks for the PR! I probably won't get time until the weekend to give it the once over and test it out. Will report back then when I do...
@toolness thanks for your offer, I'm very open to this. I'd really prefer to not break backwards compatibility if we can help it as there are some large sites with...
@porfirioribeiro thanks for the pull request. Left a few comments.
@jpoppe Thanks for these updates. On vacation 🌴 at the moment but will take a look in a week or so when I'm back. On surface all looks good 👍
Thanks for the pull request. I can see what you're looking for but not sure it's really going to work in some situations. `options` are only for openapi params which...
Yeah that's correct. Generally there will not be lots of these and the aim is to gen functions like you would write them, making the func signature readable.
Unfortunately I can't really see an easy way to implement what you're after, other than formulating a params object with the required and optional ones to put into `meta`. I'm...
@shankiesan yeah this is a valid point. It will be a breaking change when done so will require a major version bump. I'll squeeze it in next time I'm in...