René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Change the structure of object reference for the json logger","articleBody":"The issue is with how object references are currently logged, meaning StringReference, ArrayReference, and ClassReference\n\nFor example, for an array reference, the current JSON structure looks like this:\n```json\n\"reference\": {\n            \"type\": \"java.lang.String[]\",\n            \"uniqueId\": 72,\n            \"refered\": {\n              \"elements\": []\n            }\n}\n```\n\n- reference being an object reference \n- refered can be : \n   - the fields of a class reference\n   - elements of an array reference\n   - value of the String reference\nThis design makes it hard to quickly understand what kind of object we’re dealing with.\n\n**Proposal 1: Flatten the structure**\nInstead of having a generic \"reference\" object with a \"refered\" field, we can directly log the specific type of reference.\nExample for an array:\n```json\n\"ArrayReference\":{\n             \"type\": \"java.lang.String[]\",\n            \"uniqueId\": 72,\n            \"elements\": []\n}\n```\nThis way, there’s no extra “wrapper” for all ObjectReference types.\n\n**Proposal 2: Keep a wrapper but be explicit**\nIf we still want a generic ObjectReference container, we can make the type explicit inside it:\n\n```json\n\"ObjectReference\":{ \n    \"type\": \"java.lang.String[]\",\n    \"uniqueId\": 72,\n    \"ArrayReference\":{\n            \"elements\": []\n      }\n}\n```\n\nThis option could be helpfull for the importer for FamixCallStack, but is less space efficient for the outputted file","author":{"url":"https://github.com/LeoDefossez","@type":"Person","name":"LeoDefossez"},"datePublished":"2025-08-11T12:04:40.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/5/JavaCallStackExtractor/issues/5"}