frontend-analyser: Fix test xref extraction logic #2206
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Arthur Chan <arthur.chan@adalogics.com>
Signed-off-by: Arthur Chan <arthur.chan@adalogics.com>
Signed-off-by: Arthur Chan <arthur.chan@adalogics.com>
arthurscchan
force-pushed
the
fix-frontend-analyser-test-xref-logic
branch
from
a00ef18 to
87f1cd9
Compare
DavidKorczynski
approved these changes
Jun 23, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The original frontend analyser extracted the functions called by each test file and dumped the entire function profile dictionary. However, many functions were found to be redundantly or incorrectly captured, and most fields in the function profile were unused, resulting in bloated JSON output. This PR revamps the logic for test cross-reference extraction by limiting it to only the essential line numbers of function call locations, along with the initialisation and parameter definition lines for arguments used in those calls within the test or example files. This significantly reduces the size of the JSON output and provides more relevant information for web applications and OFG to process, without needing to dump the full function profile or include entire test files in the results.