[logseq-plugin-git:commit] 2025-06-19T17:22:26.455Z

pages/TOSEM-2024-0648.md

@@ -13,7 +13,6 @@ parent::
 todoist:: https://app.todoist.com/app/task/tosem-2024-0648-reviewer-agreed-6WQgFVcxWqGWQvWg
 
 	- ### [[Highlights]]
-	  collapsed:: true
 		- # Annotazioni  
 		  
 		  (16/12/2024, 12:55:04)
@@ -121,14 +120,4 @@ todoist:: https://app.todoist.com/app/task/tosem-2024-0648-reviewer-agreed-6WQgF
 			- The description of Figure 1's "Configuration box" could be expanded to include motivations for the refactoring process, such as updating third-party libraries or applying design patterns.
 			- While the paper identifies different root causes and bug symptoms, it could provide more qualitative discussions or examples to help readers understand these categories better.
 			- The distinction between "Initial preconditions" and "Final conditions checking" (e.g., for the "Make Static" refactoring) is unclear. This differentiation should be explained in greater depth.
-			- The paper mentions that the authors categorized bugs based on four aspects: 1) refactoring type, 2) root cause, 3) symptom, and 4) input characteristics, but it does not clearly explain how these labels were assigned. Explanatory examples and a discussion on the labeling process are necessary.
-		- ####
-	- ### [[REVIEWS/Notes]]
-	- ### YELLOW CONCERNS
-	  background-color:: yellow
-		- {{query (and [[ffd400]] [[TOSEM-2024-0648]] )}}
-		  collapsed:: true
-	- ### ❓️Questions
-		- {{query (and [[question]] [[TOSEM-2024-0648]] )[[question]]}}
-		  query-table:: true
-		  query-properties:: [:block]
+			- The paper mentions that the authors categorized bugs based on four aspects: 1) refactoring type, 2) root cause, 3) symptom, and 4) input characteristics, but it does not clearly explain how these labels were assigned. Explanatory examples and a discussion on the labeling process are necessary.