You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@polygene.apache.org by ni...@apache.org on 2015/12/14 03:43:05 UTC
[2/2] zest-java git commit: Fixed a reference in documentation to the
now gone Specification class.
Fixed a reference in documentation to the now gone Specification class.
Project: http://git-wip-us.apache.org/repos/asf/zest-java/repo
Commit: http://git-wip-us.apache.org/repos/asf/zest-java/commit/4dabe578
Tree: http://git-wip-us.apache.org/repos/asf/zest-java/tree/4dabe578
Diff: http://git-wip-us.apache.org/repos/asf/zest-java/diff/4dabe578
Branch: refs/heads/develop
Commit: 4dabe5781cd73463526951b70b097c2f0b45b320
Parents: c5ca22d
Author: Niclas Hedhman <ni...@hedhman.org>
Authored: Mon Dec 14 10:37:08 2015 +0800
Committer: Niclas Hedhman <ni...@hedhman.org>
Committed: Mon Dec 14 10:42:58 2015 +0800
----------------------------------------------------------------------
core/io/src/docs/io.txt | 15 +++------------
1 file changed, 3 insertions(+), 12 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/zest-java/blob/4dabe578/core/io/src/docs/io.txt
----------------------------------------------------------------------
diff --git a/core/io/src/docs/io.txt b/core/io/src/docs/io.txt
index 3abd508..dc68a99 100644
--- a/core/io/src/docs/io.txt
+++ b/core/io/src/docs/io.txt
@@ -179,18 +179,9 @@ as every 1000 items. This may not be what you think a ProgressLog should look li
how you can combine the general principles found in the Zestâ„¢ Core API package.
== How to write a filter specification? ==
-The filter transform takes a specification implementation which has a very simple method, isSatisfiedBy() (read more
-about that in <<core-functional>>.
-
-[snippet,java]
---------------
-source=core/functional/src/main/java/org/apache/zest/functional/Specification.java
-tag=specification
---------------
-
-The only thing that the implementation need to do is return *true* or *false* for whether the item passed in is within
-the limits of the Specification. Let's say that you have a IntegerRangeSpecification, which could then be implemented
-as
+The filter transform takes a regular java.util.function.Predicate as an argument, where the implementation needs to
+return *true* or *false* for whether the item passed in is within
+the limits. Let's say that you have a IntegerRangeSpecification, which could then be implemented as
[snippet,java]
--------------