{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicpwtq64imps355i2d6evqggnmr465emypqq6vuht4ok637dbyclu",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3monuligstx42"
  },
  "path": "/t/rfc-http-types-breakage-additions-rework/14286?page=2#post_22",
  "publishedAt": "2026-06-19T16:44:18.000Z",
  "site": "https://discourse.haskell.org",
  "textContent": "Vlix:\n\n>   1. Create a new major-major version of `http-types`\n>\n\n\nThis is fine… **if and only if** the previous major version will also be maintained for the foreseeable future.\n\nVlix:\n\n>   2. Add the new implementation in other modules\n>\n\n\nThis isn’t too different from 1., if we assume that both major versions would be maintained.\n\n2 would additionally allow to use both APIs at the same time. E.g. that’s a useful property in filepath, which is why I decided against solution 1 there. If that’s not a valid use case, then 1 seems more appropriate.\n\nVlix:\n\n>   3. Create a completely new package\n>\n\n\nI think there was a blog post about this. Maybe by Chris Done? But in my opinion it’s not enough as a mechanism to avoid breaking changes. There should be a general shift in goals/vision if you create a new package.",
  "title": "[RFC] \"http-types\" breakage / additions / rework"
}