René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[aws_lambda_events] Add 'catch-all' field for unmodeled fields, probably behind feature flag","articleBody":"`aws_lambda_events` is essentially a set of shadow schemas that are hand-maintained to match the event request/response types used by other services. This is very useful from a Rust perspective due to all the nice compile-time guarantees and performance optimizations we get using `serde`. However, it is very much a moving target, where schemas are always adding new fields, not to mention frequently including undocumented fields.\n\nIt would be nice to have a usage mode for 'I want the bleeding edge, including unmodeled fields'. That way, consumers could both interact with undocumented fields that we will probably never model, as well as the latest and greatest new fields even before we release a new version.\n\nWe could do that today via a 'catch-all' serde-modeled field that just is represented as a `Map\u003cString, Value\u003e`, as demonstrated here: https://github.com/serde-rs/serde/issues/941#issuecomment-375486935\n\n```\n#[derive(Serialize, Deserialize)]\nstruct S {\n    a: u32,\n    b: String,\n    #[serde(flatten)]\n    other: Map\u003cString, Value\u003e,\n}\n```\n\nAnd then the caller can interact with contained fields at runtime, or just dump it to logs.\n\nI think probably it belongs under a something like `feature = \"catch-all-fields\"` since this will involve extra allocations and other overhead?\n\nIt would be a fair bit of gruntwork to implement everywhere, but probably a LLM could do it pretty easily.","author":{"url":"https://github.com/jlizen","@type":"Person","name":"jlizen"},"datePublished":"2025-07-15T17:22:11.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/1017/aws-lambda-rust-runtime/issues/1017"}