You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/source/quark_method_reference.rst
+73Lines changed: 73 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -164,3 +164,76 @@ Here is the process of ``method_recursive_search``.
164
164
returnself.find_intersection(
165
165
next_level_set_1, next_level_set_2, depth
166
166
)
167
+
168
+
find_api_usage
169
+
==============
170
+
171
+
**The algorithm of find_api_usage**
172
+
173
+
``find_api_usage`` searches for methods with ``method_name`` and ``descriptor_name``, that belong to either the ``class_name`` or its subclass. It returns a list that contains matching methods.
174
+
175
+
Here is the process of ``find_api_usage``.
176
+
177
+
.. code-block:: TEXT
178
+
179
+
1. Initialize an empty "method_list".
180
+
2. Search for an exact match of the method by its "class_name", "method_name", and "descriptor_name".
181
+
- If found, return a list with the matching methods.
182
+
3. Create a list of potential methods with matching "method_name" and "descriptor_name".
183
+
4. Filter the list of potential methods to include only those with bytecodes.
184
+
5. Check if the class of each potential method is a subclass of the given "class_name".
0 commit comments