René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Using tag like \u003c\u003cINACCESSIBLE\u003e\u003e is problematic for moose importation","articleBody":"Actually the tags are \u003c\u003cINACCESSIBLE\u003e\u003e, \u003c\u003cCLASS_NOT_PREPARED\u003e\u003e or \u003c\u003cMAX_DEPTH_REACHED\u003e, \u003c\u003cAlready_Studied\u003e\u003e, meaning a lot of these can appear in the parsed file.\n\nWhen importing in Moose, \nit can be considered as a stringReference in some case, meaning a lot of check has to be done not to make an error.\nIt also mean comparison in String, that creates a code hard to maintain and understand.\n\nA possibility would be to add to all object that could be replaced by a tag something with an idea like this:\nFor classReference : \n```json\n\"classReference\" : {\n   \"loaded\" : true,\n   \"fields\": ...\n}\n```\n\nor \n\n```json\n\"classReference\" : {\n   \"loaded\" : false\n}\n```\n\nthis would mean an outputted file way larger, but easier to use","author":{"url":"https://github.com/LeoDefossez","@type":"Person","name":"LeoDefossez"},"datePublished":"2025-08-11T10:19:56.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/4/JavaCallStackExtractor/issues/4"}