From 28c3400175ec1be718ce4b847ccbdf238fd55e88 Mon Sep 17 00:00:00 2001 From: Ji Sungbin Date: Sat, 14 Dec 2024 18:56:03 +0900 Subject: [PATCH] Update README --- README.md | 10 ++-------- 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index 0bf7827d..0237c024 100644 --- a/README.md +++ b/README.md @@ -2,20 +2,14 @@ Trace the recomposition of a Composable with its cause without boilerplate code 😎. -This tool was initiated for personal learning and has not been proven necessary for production. +This tool was started for personal learning and has not been proven necessary for production. However, it can perform the following tasks: - **Reports if a Composable is skipped during recomposition.** - **Reports if the arguments of a Composable have changed and been recomposed.** It can also compare the values before and after the change. - **Reports if the state values inside a Composable have been modified.** It can also compare the values - before and after the change. -- **Retrieves the call stack leading up to the invocation of a Composable.** This helps identify the - specific Composable being recomposed when the same Composable is reused in multiple places. - -[*(Read the Medium's introductory post)*](https://jisungbin.medium.com/tracing-recompositions-without-boilerplate-code-e9800db1419e) - -*Next release schedule: Released when Kotlin 2.1.0 is stable* + before and after the change. *(via ComposeInvestigator's runtime plugin)* ---