Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation Feedback #77

Open
rosalieucla opened this issue Dec 14, 2017 · 3 comments
Open

Documentation Feedback #77

rosalieucla opened this issue Dec 14, 2017 · 3 comments
Assignees

Comments

@rosalieucla
Copy link
Contributor

rosalieucla commented Dec 14, 2017

Hi,

Below is feedback on the documentation. Please let us know if you have any questions.
-Rosalie

  1. Getting started > README
  • several of the file paths are incorrect, e.g. "src/app.router.ts", please fix
  • the top of the multi-line code block should have "@component({" in it
  • code snippets should use multi-line code blocks (they should not be in-line), i.e. wrap code snippets in ``` instead of `
  • please add a code snippet containing the command(s) to use for installing compodoc and generating documentation, also please note version # of both compodoc and NodeJS
  1. Modules > AppModule
  • The link to "ucla-prrla/ucla-prrla/documentation/modules/routes.html" (in the Imports table) is broken
  1. Components, Injectables > SolrService, Pipes
  • All class properties should have:
    • public/private annotation (if applicable) that will appear in the documentation
    • type annotation that will appear in the documentation. For example, several of the AdvancedSearchComponent properties ("availableOrders", "initializing_first_time", etc.) do not show any type in the documentation
    • JSDoc with a clear, concise, unambiguous description of the property. For example, several of the AdvancedSearchComponent properties already have JSDocs with descriptions, but they are not clear enough (too many words is better than not enough words)
      • bad: "Available Orders", "Selected Filters"
      • better: "Flag that indicates if page is initializing or not"
  • All class methods should have:
    • JSDoc with:
      • a clear, concise, unambiguous description of what the method does
      • @param annotation for each parameter, with name, type, and description, with a hyphen before the description: see http://usejsdoc.org/tags-param.html
      • @returns annotation, if there is a return value
@Hlopec
Copy link
Contributor

Hlopec commented Jan 5, 2018

Hi all,
Please take a look on this.

@markmatney
Copy link
Contributor

markmatney commented Jan 12, 2018

@Hlopec,

Thanks for the update. Items 1 and 2 look good. As for item 3: can you complete the JSDocs in the following components please (particularly, the method parameters with type annotations and descriptions, and method return values)?

  • ExhibitionComponent
  • ExhibitionsComponent
  • HelpComponent

@saslv
Copy link
Contributor

saslv commented Jan 15, 2018

Done. Please check.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants