Menu

#2397 shortcomings of new javadoc generation

nextrelease
open
nobody
None
5
2025-04-09
2021-10-07
No

About a year ago there was an effort to make a version of the JavaDoc which could be put onto a github site so that many people could maintain it. There are shortcomings I notice as I'm going through and reviewing this output. This ticket will enumerate.

Discussion

  • Jeremy Faden

    Jeremy Faden - 2021-10-07

    Single quotes, like "reduce the dataset's rank" cause the summary to break at the quote. See http://www-pw.physics.uiowa.edu/~jbf/autoplot/doc/index-all.html, reduceMax.

     
  • Jeremy Faden

    Jeremy Faden - 2021-10-07

    expm1's

    Returns <i>e</i><sup>x</sup>&nbsp;-1.
    

    breaks the line.

     

    Last edit: Jeremy Faden 2021-10-07
  • Jeremy Faden

    Jeremy Faden - 2021-10-07

    Often if there's an undocumented f(Object) and f(QDataSet) no documentation is used. I can't recall how it decides which signature to show, but this should be revisited. See stddev(O)

     

    Last edit: Jeremy Faden 2021-10-07
  • Jeremy Faden

    Jeremy Faden - 2021-10-07

    Many of the functions result in no javadoc.

     
  • Jeremy Faden

    Jeremy Faden - 2021-10-07

    See https://github.com/jbfaden/MarkdownDoclet , which is the project where this is implemented.

     
  • Jeremy Faden

    Jeremy Faden - 2021-10-25
     
  • Jeremy Faden

    Jeremy Faden - 2025-04-09

    Sadie didn't like how multiple var-args functions were coalesced. For example, findgen(int) and findgen(int,int) would show the same documentation. This was confusing for things like fftPower where the different modes were not shown.

    I've made it so this no longer happens, but the javadocs will be inconsistent when Autoplot version v2025a_3 or earlier is used.

     
MongoDB Logo MongoDB