-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding documentation for functions with multiple parameters? #241
Comments
Not sure why it won't compile 🤔 I'll check it out. generally if you have many args, using a record as input with named fields will be much better since you can see what is what more clearly |
Yes, I have that approach working seperately (with a pattern of TRequest -> Async), I just wasn't sure if this approach was supposed to work or not Thanks |
Hi @Numpsy is this issue still valid? can you please give it another go with latest packages? |
I'll give it a try later. |
Hi, |
I'm also experiencing this issue. I also can't see any examples in the documentation UI. |
Hi @vKito the issue still stands I believe. As a temp workaround you can either use a record with named fields or a tuple |
Isn't the problem simply the fact that there's support only for 1 and 2 parameter functions? I guess it's not possible to generalize this with an expression taking functions with arbitrary arity? |
Yup, I refactored my endpoint to accept a single value instead. Works this way thanks. At the same time I feel the need to point out a gotcha with the examples: This is more a general quoted expression gotcha but I thought I would point it out for anyone needing help. If you pass in values that get computed at runtime, e.g. GUIDs, then the docs UI won't show any examples, but everything still compiles fine.
The woraround to this is to simply create the GUID outside the quoted expression
|
Hi,
Say that I have this example from the documentation:
I tried plugging in documentation entries for that, and got:
Should that work, or am I doing something silly?
Thanks
The text was updated successfully, but these errors were encountered: