From c8a66fbe73b455c89823956e317ba30cc7a99322 Mon Sep 17 00:00:00 2001
From: kageru <kageru@encode.moe>
Date: Sat, 4 Jul 2020 01:00:18 +0200
Subject: [PATCH] use Tuple2::apply instead of field access

---
 src/main/java/nouritsu/Nouritsu.java | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/src/main/java/nouritsu/Nouritsu.java b/src/main/java/nouritsu/Nouritsu.java
index df65810..4ec7d21 100644
--- a/src/main/java/nouritsu/Nouritsu.java
+++ b/src/main/java/nouritsu/Nouritsu.java
@@ -87,20 +87,20 @@ public class Nouritsu extends NanoHTTPD {
     return getAsTuple(params, "user", "item")
       // This is where Kotlin-like destructuring would be really nice to have:
       // flatMap(id, item -> ...)
-      .flatMap(t -> dao.addToList(t._1, t._2))
+      .flatMap(t -> t.apply(dao::addToList))
       .fold(Function.identity(), Resp.CREATED);
   }
 
   private static Resp addItem(Map<String, String> params, Dao dao) {
     return getAsTuple(params, "name", "category")
-      .flatMap(t -> ShoppingItem.tryParse(t._1, t._2))
+      .flatMap(t -> t.apply(ShoppingItem::tryParse))
       .map(dao::addItem)
       .fold(Function.identity(), Resp.CREATED);
   }
 
   private static Resp addStore(Map<String, String> params, Dao dao) {
     return getAsTuple(params, "name", "categories")
-      .flatMap(t -> Store.tryParse(t._1, t._2))
+      .flatMap(t -> t.apply(Store::tryParse))
       .flatMap(dao::addStore)
       .fold(Function.identity(), Resp.CREATED);
   }