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}




Comments

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

Application Design Notes

Don’t be afraid to write your own code, but be absolutely sure you need to Don't reinvent the wheel Learn more about your libraries and take full advantage  Date time calculation is hard ( leap second ,  leap year ), use trusted library  js-joda ,  momentJs ,  joda (java) Simple is better than perfect (nearly) every time If you can deliver a sub-optimal solution (that solves the problem but has known limitation) in a week instead of a full featured one in a month DO, IT Simple system are Easy to reason about  Easy to debug Easy to refactor Easy to learn Simple doesn't mean you skip good engineering, but you can use duct tape. Build things the right way from the start, refactoring is hard and expensive Security Manage and store passwords securely Telemetry Common retrofitting "grunt work" Internationalization + localization Web Content Accessibility Factoring and styling HTML UI Adding unit test to an existing codebase LOG LOG LOG Log, but do it right We spend lot of t

How to store user password at server!!!

Trick is, you should never store user password… never ever. Now the real question is, then how to authenticate and authorize the user with password. And answer is when user enter the password, we should encrypt the password and store the hints. So next time when user enter the password we follow the same process and compare hints, if both hints are same then password is matched, else it is wrong password. Next question will be, what kind of hints, and how to generate these hints. In simple term hints are the obfuscated and fragmented form of user password. And very important part is hints generation process, which have to be collision resistant , means there will be very less possibility to find the data which generate same hints (like Cryptographic hashing functions ). Below is the simple checklist of password hashing and storing, which you should always keep in mind. PS You're Probably Storing Passwords Incorrectly Storing Passwords - done rig