Could you please add function signatures for lambda functions such as array.filter's to the docs?

[aarnent]

@typssst

sometimes I wonder if a function takes (index, val) or only (index)

That’s fair, but in case you didn’t know a helpful tip for debugging is that you can hover over the variables to see their value. So for example, if you’re unsure how many arguments a function should take you can use the .. sink operator and hover over the value to see what the arguments are

See also Tips on debugging Typst code, including the dark magic

@typssst

Or if they take (x, y) or also (top, right, bottom, left)—e.g. in some of the functions that can be passed to table.

I guess you refer to parameters like inset that take in arrays or dictionaries, not functions. I agree that it is kind of hidden, but the docs link to box’s inset. I’d imagine this is done both to avoid duplication and errors if the API were to change in the future.

@typssst

Ideally it should be done automatically (maybe by annotating them in the Rust code) and using a Doxygen-like tool to generate the API docs.

I could see something like this being done, and I quite like the suggestion. I don’t know how feasible it is, but I’d imagine the maintainers (which you can reach better by opening an issue on github or even asking on the discord) would know