Scala Programming Language
  1. Scala Programming Language
  2. SI-5054

Scaladoc: hide complex definitions behind use cases

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Scaladoc Tool

      Description

      Scaladoc: hide complex definitions behind use cases rather than showing both the complex definition and use cases

        Activity

        Hide
        Daniel Sobral added a comment -

        The methods are being shown as "abstract". Also... how can I see the actual signature? I see Simon complaining that the signature shows up in the body, but I don't see it at all!

        Show
        Daniel Sobral added a comment - The methods are being shown as "abstract". Also... how can I see the actual signature? I see Simon complaining that the signature shows up in the body, but I don't see it at all!
        Hide
        Vlad Ureche added a comment -
        • I looked into the abstract use cases problem and it was always like this – see the 2.9.1 scaladoc for List, the ++ use case has Attributes: abstract, but it's not shown in the signature. We can hide them again, no problem
        • the full signature is contained in the model, but the html generation needs a bit of tweaking to show it
        Show
        Vlad Ureche added a comment - I looked into the abstract use cases problem and it was always like this – see the 2.9.1 scaladoc for List, the ++ use case has Attributes: abstract, but it's not shown in the signature. We can hide them again, no problem the full signature is contained in the model, but the html generation needs a bit of tweaking to show it
        Hide
        Daniel Sobral added a comment -

        Actually, I know, but the actual method wasn't hidden then. At any rate, the method in the use case does not exist, so no attributes makes sense for it. Instead, it should assume the attributes of the method it is actually "overriding", so to speak.

        Show
        Daniel Sobral added a comment - Actually, I know, but the actual method wasn't hidden then. At any rate, the method in the use case does not exist, so no attributes makes sense for it. Instead, it should assume the attributes of the method it is actually "overriding", so to speak.
        Hide
        Vlad Ureche added a comment -

        Fixed in pull request 46.

        Show
        Vlad Ureche added a comment - Fixed in pull request 46.
        Hide
        Vlad Ureche added a comment -

        Fixed everything some time ago, the only piece missing from the puzzle is SI-5291.

        Show
        Vlad Ureche added a comment - Fixed everything some time ago, the only piece missing from the puzzle is SI-5291 .

          People

          • Assignee:
            Vlad Ureche
            Reporter:
            Vlad Ureche
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development