Skip to main content

Guava: Function, Predicate and Ordering



Function and Predicate are just interfaces but plays key roll in many use-cases.

Function: Determines an output value based on an input value
Predicate: Determines a true or false value for a given input.
Ordering: It's a comparator with added methods to support common functions.

Assume we have some User Object List
User{firstName=userA, lastName=B, salary=1234567.0}
User{firstName=userB, lastName=C, salary=1234577.0}
User{firstName=userB, lastName=D, salary=1234777.0}
User{firstName=userE, lastName=A, salary=1237777.0}
User{firstName=userD, lastName=A, salary=1237778.0}
User{firstName=userA, lastName=D, salary=1237788.0}


User Function Class
public enum UserFunctions implements Function<User, String>{
 FIRSTNAME{
  @Override
  public String apply(User user){
   return user == null ? "" : user.getFirstName();
  }
 },

 LASTNAME{
  @Override
  public String apply(User user){
   return user == null ? "" : user.getLastName();
  }
 },

 FIRSTNAME_LASTNAME{
  @Override
  public String apply(User user){
   return user == null ? "" : user.getFirstName() + " " + user.getLastName();
  }
 };
}


User Predicates Class
public enum UserPredicates implements Predicate<User>{
 FIRSTNAME_END_WITH_VOWEL {
  @Override
  public boolean apply(User user) {
   if(user == null){return false;}
   String firstName = user.getFirstName();
   return asList('a', 'e', 'i', 'o', 'u')
    .contains(firstName.toLowerCase().charAt(firstName.length()-1));
  }
 };
}


User Ordering Class
public class UserOrdering { 
 public static Ordering<User> BY_FIRST_NAME = 
  Ordering.natural().onResultOf(UserFunctions.FIRSTNAME);
  
 public static Ordering<User> BY_LAST_NAME = 
  Ordering.natural().onResultOf(UserFunctions.LASTNAME);
  
 public static Ordering<User> BY_FIRSTNAME_THEN_LASTNAME = 
  BY_FIRST_NAME.compound(BY_LAST_NAME);
 
 public static Ordering<User> BY_SALARY = 
  Ordering.natural().onResultOf(
   new Function<User, Float>(){
    @Override
    public Float apply(User user){
     if(user == null){return 0F;}
     return user.getSalary();
    }
   }
  );
}


One of the best part about the predicate, function and ordering is usability. It separate the repetitive code in well encapsulated classes which can be used in many diff. places. So you don't have to write the boilerplate code each time and it make your code much smaller and readable.

Here are few useful scenarios

User with maximum salary 
User user = Collections.max(userList, UserOrdering.BY_SALARY);

Output:->
User{firstName=userA, lastName=D, salary=1237788.0}


Retrieve the list of "firstName lastName" from the user list
Collection<String> userList = Collections2.transform(
                          userList, UserFunctions.FIRSTNAME_LASTNAME);

Output:->
userA B
userB C
userB D
userE A
userD A
userA D


Divide the user list in group of 3 and extract the second group
int pageSize = 3;
int pageIndex = 1;
List<User> userList = Lists.partition(userList, pageSize).get(pageIndex); 

Output:->
User{firstName=userE, lastName=A, salary=1237777.0}
User{firstName=userD, lastName=A, salary=1237778.0}
User{firstName=userA, lastName=D, salary=1237788.0}


Filter the user where first name ends with vowel
Predicate<User> allPredicate = Predicates.and(
 Predicates.<User>notNull(), 
 UserPredicates.FIRSTNAME_END_WITH_VOWEL);
  
Collection<User> userList = Collections2.filter(userList, allPredicate);

Output:->
User{firstName=userA, lastName=B, salary=1234567.0}
User{firstName=userE, lastName=A, salary=1237777.0}
User{firstName=userA, lastName=D, salary=1237788.0}


Sort the user list with first name then last name
Collections.sort(userList, UserOrdering.BY_FIRSTNAME_THEN_LASTNAME);

Output:->
User{firstName=userA, lastName=B, salary=1234567.0}
User{firstName=userA, lastName=D, salary=1237788.0}
User{firstName=userB, lastName=C, salary=1234577.0}
User{firstName=userB, lastName=D, salary=1234777.0}
User{firstName=userD, lastName=A, salary=1237778.0}
User{firstName=userE, lastName=A, salary=1237777.0}




Popular posts from this blog

ERROR: Ignored call to 'alert()'. The document is sandboxed, and the 'allow-modals' keyword is not set.

Recently I found this issue while writing code snippet in "JSFiddle". And after searching, found this was happening because of new feature added in "Chrome 46+". But at the same time Chrome doesn't have support for "allow-modals" property in "sandbox" attribute.

Chromium issue for above behavior:
https://codereview.chromium.org/1126253007

To make it work you have to add "allow-scripts allow-modals" in "sandbox" attribute, and use "window.alert" instead of "alert".



<!-- Sandbox frame will execute javascript and show modal dialogs --> <iframe sandbox="allow-scripts allow-modals" src="iframe.html"> </iframe>


Feature added: Block modal dialog inside a sandboxed iframe.
Link: https://www.chromestatus.com/feature/4747009953103872

Feature working Demo page:
https://googlechrome.github.io/samples/block-modal-dialogs-sandboxed-iframe/index.html



CSS Specificity

Many time different CSS rules overlap on one or more element. And some people always get confuse about, which rule will take higher priority then other and why? CSS Specificity is the answer of all these kind of questions.
As the name suggest, the CSS rule which is more specific to the element will take higher priority then other. Means something like “#some_id{}” will always take higher priority then “*{}” universal selector.  And if duplicate rules are define then the last rule will be applied to the element.

The following list of selectors is by increasing specificity:
Type selector (e.g., div) and pseudo-elements in selector (e.g., :after) Class selectors (e.g., .some_class), attributes selectors (e.g., [type=”radio”]) and pseudo-class selector (e.g., :hover) Id selectors (e.g., #some_id)


ID takes higher priority then Class, Type and Universal selector (Note: Universal selector has no effect on specificity, see below special conditions). 



If duplicate rules are given, then last…

Guava: Some useful IO utilities

Guava IO package provides very useful utility classes for input/ouput stream, byte stream, file handling and many more. Here are few example which show case how these utilities can make your code much cleaner, modular and more readable.Copy “InputStream” to “OutputStream InputStream is = CopyStreams.class.getResourceAsStream("test.txt"); OutputStream os = System.out; ByteStreams.copy(is, os);Changing InputStream to “byte[]” InputStream is = CopyStreams.class.getResourceAsStream("test.txt"); byte[] isBytes = ByteStreams.toByteArray(is); // Now if you want to get base64 encoded string then it will be like this String isBase64Str = new sun.misc.BASE64Encoder().encode(isBytes);Combining two files in one File input1 = new File("c:\\testio\\AWords.txt"); File input2 = new File("c:\\testio\\BWords.txt"); File output = new File("c:\\testio\\ABWords.txt"); …