alamb commented on issue #9173: URL: https://github.com/apache/arrow-datafusion/issues/9173#issuecomment-1936549150
Thank you @ongchi -- I think this is a *really* great idea. Thank you Here is a similar issue from @andygrove https://github.com/apache/arrow-datafusion/issues/7951 that also has a PR https://github.com/apache/arrow-datafusion/pull/7956 As a pragmatic matter, here is my suggestion for incrementally implementing this without having to make a massive PR that will be a conflict magnet. First, we accept that there will be a period of time where we have a split set of documentation (one auto generated, and one static) Then, build the new automatic documentation system you describe based on the functions in https://github.com/apache/arrow-datafusion/tree/main/datafusion/functions (it is a subset at the moment). That way we can get the tooling and pattern sorted out. Then as we migrate the rest of the functions over, we can migrate the documentation as well -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
