René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[BUG] Golang - When using import mappings, import mapping is not properly generated when using composition plus slice pointer type","articleBody":"one.yaml\n```\nschemas:\n  Thing:\n          type: object\n          properties:\n           Property: value\n  Example:\n    properties:\n      Thing\n        type: array\n        items: $ref \"#/components/schemas/Thing\"\n          \n```\ntwo.yaml\n```\nschemas:\n   MyThing:\n     allOf:\n       - $ref: \"one.yaml#/components/schemas/Example'\n       - type: object\n          properties: # whatever one might add here...\n```\n\nOutput when generating two.yaml:\n```\ntype MyThing struct {\n    Thing *[]Thing\n}\n```\nExpected output generating two.yaml:\n```\ntype MyThing struct {\n    Thing *[]externalRef0.Thing\n}\n```\n\n##### Steps to reproduce\n1) create two specs, one referencing the other\n2) Reference a slice type from 1 to another\n3) *optional* reference a non slice type to see desired behavior\n4) write configuration file to point import mapping of spec 2 to spec 1's output generation\n5) Run the generator\n\n##### Suggest a fix\n\nUse same external mapping logic when type is a slice pointer.\n","author":{"url":"https://github.com/chaslain","@type":"Person","name":"chaslain"},"datePublished":"2025-06-20T18:28:36Z","url":"https://github.com/oapi-codegen/oapi-codegen/issues/2008"}