Closed MilesCranmer closed 6 hours ago
Sure sounds good. Could we just add another argument to the macro?
A PR would be great
Done! In #47
Thanks for merging! Could you also publish a new release so I can use this wonderful new feature? 🙂
(I see the patch bump – thanks! Do you think you could trigger registrator?)
Sorry I'm on the road all week and cant comment on commits from my phone. But I should have a laptop open later tonight.
No worries!
(If you can't click the commit, here's the link: https://github.com/rafaqz/Interfaces.jl/commit/e0243ed953aa7d7ac302bd63449e37667e791262 https://github.com/rafaqz/Interfaces.jl/commit/e0243ed953aa7d7ac302bd63449e37667e791262
😁 )
Done!! (the github app just doesn't allow commenting on commits, no idea why... and my phone also forces all github urls to the app)
Awesome, cheers! 🍺
Hey @rafaqz,
I was wondering if there was a way to generate "Extended help" documentation for an interface? As described in https://docs.julialang.org/en/v1/manual/documentation/#Writing-Documentation there is this special
# Extended help
trigger:I think this would be useful for very long interfaces. For example,
DynamicExpressions.ExpressionInterface
has 20 functions to implement (implementation here), including the optional ones. I could see this being overwhelming for someone to go look up each of the docstrings for each, so I'm wondering if maybe the generated docs for an interface could include all the component descriptions?Right now, the help (with a single
?
):is the same as extended help (double
??
):I think the extended help could be a good chance to include all component descriptions. What do you think?
Cheers, Miles