-
Notifications
You must be signed in to change notification settings - Fork 27.4k
Conversation
I saw that the uppercase filter had no example so I decided to add a minimal example to explain how the uppercase filter works.
Thanks for the PR! Can you please make these 2 changes:
|
I remove the protractor file and added |
@Narretz is this appropriate on the whole or would you like me to change this? |
src/ng/filter/filters.js
Outdated
@@ -709,6 +710,22 @@ var lowercaseFilter = valueFn(lowercase); | |||
* @kind function | |||
* @description | |||
* Converts string to uppercase. | |||
* @see angular.uppercase | |||
* @example | |||
<example name="filter-uppercase"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you must add module=uppercaseFilterExample
, otherwise the example won't work
src/ng/filter/filters.js
Outdated
@@ -699,6 +699,7 @@ function jsonFilter() { | |||
* @description | |||
* Converts string to lowercase. | |||
* @see angular.lowercase | |||
* @see angular.uppercase |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The docs don't actually do anything with @see
:(, please revert this change
@@ -699,6 +699,7 @@ function jsonFilter() { | |||
* @description | |||
* Converts string to lowercase. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add a link after this that points to uppercase: Format is {@link ng.filter.uppercase linktext}
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored by someone other than the pull request submitter. We need to confirm that they're okay with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the |
1 similar comment
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored by someone other than the pull request submitter. We need to confirm that they're okay with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the |
Thanks - I fixed the link myself because I gave you the wrong path ;) |
I saw that the uppercase filter had no example so I decided to add a minimal example to explain how the uppercase filter works.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Docs update.
What is the current behavior? (You can also link to an open issue here)
There is currently no example for the
uppercase
filter, so I added one.What is the new behavior (if this is a feature change)?
N/a
Does this PR introduce a breaking change?
No.
Please check if the PR fulfills these requirements
Other information: