From 2aa0c7ed7b3bb1a4057e5dfd7a81681d28409013 Mon Sep 17 00:00:00 2001
From: Jueun Park <s5616012@mailbox.tu-dresden.de>
Date: Thu, 14 Oct 2021 01:58:15 +0900
Subject: [PATCH] Update

---
 sections/stm2.tex | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/sections/stm2.tex b/sections/stm2.tex
index ef4cf86..ac9bf95 100644
--- a/sections/stm2.tex
+++ b/sections/stm2.tex
@@ -46,7 +46,7 @@ During the implementation phase of parameter inference, RAG was beneficial at wr
 
 \begin{itemize}
 \item As long as a returned type can be called or storable in primitive way, the syntax in RAG is reduced with an equlas sign and simpler than in common programming language. Therefore, the source codes are compact. To compare how RAG could be implemented effectively, see the implementation of an attribute in this work in Listing 5.3 and how this attribute is defined in common Java description in Listing 5.4.
-\item For loop with inherited attributes
+\item To iterate all paths available in OpenAPI, an inherited attribute facilitated the writing effort. Paths Objects are child nodes of OpenAPI Object, so, all that should have been done was only two lines of code instead of writing an extra for loop. See Listing 5.5.
 \item Collection attributes
 \end{itemize}
 
@@ -60,6 +60,13 @@ public String InferredParameter.value() {
 }
 \end{lstlisting} 
 
+\begin{lstlisting}[language=JRAG,label={lst:java-infParam},caption={InferredParameter.value() in Java}]
+inh boolean PathsObject.inferUrl();
+eq OpenAPIObject.getPathsObject(int i).inferUrl(){
+  ...
+}
+\end{lstlisting} 
+
 % Result
 
 % Future work
-- 
GitLab