https://famer.me/tags/Play-Framework/Recent content in Play Framework on My SpaceHugoenThu, 13 May 2021 18:37:55 +0800https://famer.me/2021/05/13/After-I-migrated-my-legacy-playframework-project-to-zio-what-I-learned-from-it/Thu, 13 May 2021 18:37:55 +0800https://famer.me/2021/05/13/After-I-migrated-my-legacy-playframework-project-to-zio-what-I-learned-from-it/<ul> <li><a href="#foreword">Foreword</a></li> <li><a href="#what-is-r">What is <code>R</code></a></li> <li><a href="#what-are-the-problems-caused-by-di-tools">What are the problems caused by DI tools?</a></li> <li><a href="#current-situation">Current Situation</a></li> <li><a href="#evolution-stage-1">Evolution Stage 1</a></li> <li><a href="#evolution-stage-2">Evolution Stage 2</a></li> <li><a href="#evolution-stage-3">Evolution Stage 3</a></li> <li><a href="#conclusion">Conclusion</a></li> <li><a href="#references">References</a></li> </ul> <h1 id="foreword">Foreword</h1> <p>On April 17, 2020, I start a huge project to migrate the <code>Future[T]</code> from legacy playframework project to <code>ZIO</code>. Three months later, after tens of thousands of lines of code modification, the migration was a complete success. In September, I used this experience as the background to share in the Chinese Scala Meetup community with the title <a href="https://www.slideshare.net/ssuser81d309/scala-meetup-248313493">&ldquo;Introduction to ZIO&rdquo;</a>. In this share, I explained a fanatic imageation, 在这次分享中，我展望了一个美好的愿景，借由 <code>ZIO</code> 的类型参数 <code>R</code> 提供的抽象能力来实现代码的可移植性，和提高可测试性。但想在遗留项目中实现这个愿景并不容易，主要挑战来自遗留项目的代码耦合，和开发者的思维惯性。如今，这个愿景已经达成。我会在这篇 Post 中与你分享我的进化之路。</p>