Repository navigation
API doc for pipes - #24141
API doc for pipes#24141jbogarthyde wants to merge 4 commits into
Conversation
|
@petebacondarwin FYI |
|
You can preview f8e6cbb at https://pr24141-f8e6cbb.ngbuilds.io/. |
|
You can preview e3d0b77 at https://pr24141-e3d0b77.ngbuilds.io/. |
33c65d1 to
db133ab
Compare
|
You can preview db133ab at https://pr24141-db133ab.ngbuilds.io/. |
|
You can preview c06c867 at https://pr24141-c06c867.ngbuilds.io/. |
|
You can preview dd0d78c at https://pr24141-dd0d78c.ngbuilds.io/. |
dd0d78c to
4b9b3c3
Compare
|
You can preview 4b9b3c3 at https://pr24141-4b9b3c3.ngbuilds.io/. |
jenniferfell
left a comment
There was a problem hiding this comment.
Approved with one change: Please change to "deprecated in v5" or similar (v "from v5").
Other comments....Please file an issue against caps style in auto-generated headings. Of my other comments, the rest are minor editorial.
There was a problem hiding this comment.
whitespace-separated word
There was a problem hiding this comment.
No comma when second clause is dependent. "The pipe uses the Internationalization API and is therefore only reliable in Chrome and Opera browsers."
There was a problem hiding this comment.
"and so on" - delete? change to "or other formatting characteristics"?
There was a problem hiding this comment.
Predefined (one word)
There was a problem hiding this comment.
Did you want en-US in single quotes or backticks or none? Above "en-US locale" has no special treatment. Let's standardize how to handle locale names. You choose.
There was a problem hiding this comment.
I think we should use sentence case in table column headers, so it matches heading cap style everywhere else in docs.
There was a problem hiding this comment.
Need to file an issue. Usage notes heading should be sentence caps, not title caps.
There was a problem hiding this comment.
Need to file an issue. Input values heading should be sentence caps, not title caps.
|
@jbogarthyde If this is no longer just to test the new template and generator, pls update the title. Thanks! |
|
You can preview e2b9786 at https://pr24141-e2b9786.ngbuilds.io/. |
|
We are still testing the template, leaving title alone. |
|
You can preview 1595762 at https://pr24141-1595762.ngbuilds.io/. |
|
You can preview de04249 at https://pr24141-de04249.ngbuilds.io/. |
9a4c770 to
46097e4
Compare
|
You can preview 46097e4 at https://pr24141-46097e4.ngbuilds.io/. |
There was a problem hiding this comment.
I would replace
+ * @param value The string to transform, with words delimited by any whitespace character,
+ * such a space, tab, or line-feed character.
with
+ * @param value The text to convert to lower case.
I don't think trying to define what a "word" is helps and I'm not sure if this is correct definition anyway.
There was a problem hiding this comment.
oops - wrong one, this should only be in title-case. Removing it.
There was a problem hiding this comment.
Sounds like we are repeating the same thing twice ?
Replace whitespace-separated word with word as the former is wrong.
There was a problem hiding this comment.
Not sure how this get rendered but the text itself adds no value IMO.
There was a problem hiding this comment.
It is a general rule of our new API guidelines that all code examples should be introduced with a text description of what the code is an example of. In this case, it doesn't add a whole lot of value, but it is still required.
There was a problem hiding this comment.
Most code examples show some specific thing -- it helps the reader know where to look in the code if you first tell them what it is supposed to show. This is part of reducing cognitive load for the reader, by making each point as explicit as possible.
There was a problem hiding this comment.
same comment as earlier. I would use @param value The text to convert to title case
There was a problem hiding this comment.
For TitleCasePipe it might be valueable to explicitly mention that whitespace is used as the separator, especially since the behavior was different in the past (e.g. - where treated as boundaries, but not any more).
There was a problem hiding this comment.
still confusing/wrong.
each locale has 2 sets of data: the "regular" one and the "extra" one. * means the extra one, this is what the former description stated.
There was a problem hiding this comment.
in the _local_ time this was important too
vicb
left a comment
There was a problem hiding this comment.
Thanks for the updates.
A few more comments
3530aaa to
bc59b64
Compare
bc59b64 to
11c61a6
Compare
|
You can preview a4f7473 at https://pr24141-a4f7473.ngbuilds.io/. |
|
Addressed comments, and some more small fixes. |
|
You can preview de33116 at https://pr24141-de33116.ngbuilds.io/. |
|
You can preview 449373b at https://pr24141-449373b.ngbuilds.io/. |
|
@vicb @ocombe |
|
If I may (and @ocombe will correct me if I'm wrong), I think the docs for the currency pipe should also mention that if I can submit a PR if you agree (unrelated, but I think there is an error in the example https://github.com/angular/angular/blob/master/packages/examples/common/pipes/ts/currency_pipe.ts#L21) |
|
That is true, the number of digits for rounding depends on the locale |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
Does this PR introduce a breaking change?