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

docs(common): migrate deprecated jsdoc tags #23062

Closed

Conversation

petebacondarwin
Copy link
Member

No description provided.

@petebacondarwin petebacondarwin added action: review The PR is still awaiting reviews from at least one requested reviewer target: major This PR is targeted for the next major release labels Mar 29, 2018
@mary-poppins
Copy link

You can preview c41642d at https://pr23062-c41642d.ngbuilds.io/.

* @description
*
* Formats a number as percentage.
* Uses the function {@link formatPercent} to format a number as a percentage according
* to locale rules.
*
* Where:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In cases like this, the description reds fine in source code, but when this will be split up in the docs, the where:... part will be out of context.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not actually as bad as you may think due to the params section being directly above...

screen shot 2018-03-29 at 15 26 34

But the next step is to move these descriptions into the actual parameters of the transform function.
I can do that in this PR too to show how it would work.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It was just an example. I have seen it in another PR a few days ago.
My point is that people will write docs in a way that will read fine in the comment, but not so fine in the docs template.

Let's hope that all reviewers will actually look at the preview 😛

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

True but that is true of all docs, right. Like putting bad headings or crazy tables.
We should just ensure that reviewers actually look at the preview.
I have updated all the Pipes to put the param descriptions in the right place as an example of how to do this.

If we keep the amount of "general" description that people have to write to a minimum then we should be able to control how it looks better. The worst scenarios are when people feel they have a blank canvas and start trying to do their own "formatting".

@mary-poppins
Copy link

You can preview b52b8b3 at https://pr23062-b52b8b3.ngbuilds.io/.

@mary-poppins
Copy link

You can preview ec9ffab at https://pr23062-ec9ffab.ngbuilds.io/.

@IgorMinar
Copy link
Contributor

@petebacondarwin you'll need to update the public api guard (that is now part of the angular monorepo) to not complain about the missing @stable markers. the rest looks great.

@IgorMinar IgorMinar added action: cleanup The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Mar 29, 2018
@IgorMinar
Copy link
Contributor

In pipes the content of these tags is now generated automatically.
In directives these tags have been converted to `@usageNotes` tags,
but in the future me might find a way to generate that usage too.
We get the overview for the doc by splitting off the first
paragraph.
@petebacondarwin petebacondarwin added action: review The PR is still awaiting reviews from at least one requested reviewer area: common Issues related to APIs in the @angular/common package type: docs and removed action: cleanup The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews labels Mar 30, 2018
@IgorMinar IgorMinar added action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Apr 5, 2018
@IgorMinar IgorMinar closed this in 46ba7f6 Apr 5, 2018
IgorMinar pushed a commit that referenced this pull request Apr 5, 2018
We get the overview for the doc by splitting off the first
paragraph.

PR Close #23062
IgorMinar pushed a commit that referenced this pull request Apr 5, 2018
@petebacondarwin petebacondarwin deleted the aio-update-common-docs branch April 5, 2018 16:37
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker area: common Issues related to APIs in the @angular/common package cla: yes target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants