René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Remove the `insertAutoGeneratedEnumMappings` gradle task","articleBody":"The idea is to remove the `insertAutoGeneratedEnumMappings` task. This task currently runs stitchs `CommandProposeV2FieldNames` to generate names from the non-stripped enum variants (at least that's what I think it does). Removing this would require us to map these enum variants ourself. This is not hard, we already do this (I think).\r\nIn for example 1.12.2 the task only replaced 16, but detected 2184 \"interesting names\".\r\nIn 12w30e-client it replaced 0  names, and detected 130 \"interesting names\".\r\n\r\nTherefore I think we should just remove that task and simpify the building process.\r\n\r\nIn the image you can see what would be replaced: the two red arrows to and the one from the `insertAutoGeneratedEnumMappings` task would be replaced with the green one that directly connects `buildFeatherTiny` with `v2UnmergedFeatherJar`.\r\n![image](https://github.com/OrnitheMC/feather-mappings/assets/67289119/4f093671-c0a6-4cd2-b9be-1ebba47da553)\r\nNote: I plan to open a PR in the future containing that graph.\r\n\r\nIn terms of code changes:\r\nThe task to be removed is:\r\nhttps://github.com/OrnitheMC/feather-mappings/blob/e28cce1fb4853702bb8e9b68cdc5829a17a1a68e/build.gradle#L1079-L1098\r\nThis would require changes in the `v2UnmergedFeatherJar` task:\r\nhttps://github.com/OrnitheMC/feather-mappings/blob/e28cce1fb4853702bb8e9b68cdc5829a17a1a68e/build.gradle#L1130-L1140\r\nMainly the `dependsOn` would need to change to `buildFeatherTiny`, and `def mappings` also needs to use `buildFeatherTiny`.\r\n\r\nThis issue is created to discuss how much this would break, since I do not currently know how dependant the mappings are on this feature.\r\n\r\nfor the future PR: (just using this as notes for later on)\r\n- Remove the `insertAutoGeneratedEnumMappings` gradle task and instead map these directly; see #142\r\n I do not yet know the impacts of this, see the issue for this.\r\n... maybe there's more that could be cleaned up:\r\n- Why do we use tiny v1 in so many places? We should just switch all to tiny v2 and generate tiny v1 from them.","author":{"url":"https://github.com/zeichenreihe","@type":"Person","name":"zeichenreihe"},"datePublished":"2023-10-21T21:29:31.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/142/feather/issues/142"}