{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiamjfnci62z4lhlhvuum73mbmhwfevqtsh3ucfxgeb4exepvhrvcu",
    "uri": "at://did:plc:dxjzgxe7cvirxkwfjr2tjspt/app.bsky.feed.post/3mgw27ilhpsc2"
  },
  "path": "/t/ai-created-changes-should-it-create-prs-or-work-on-my-own-fork/49434#post_12",
  "publishedAt": "2026-03-12T14:18:48.000Z",
  "site": "https://hub.jmonkeyengine.org",
  "textContent": "At one time, I had mapped out a multistep process to convert the vertex buffer type from being an enum to just being a class that had information in it… with a bunch of preset constants for the existing enum values. I can’t find those notes anymore but it was something like:\n\n  1. convert VerextBuffer.Type to a real class with a set of constants representing the current enum values.\n  2. deal with the collateral damage\n  3. add the binding name to VertexBuffer.Type and stop auto-generating it. (I wouldn’t even automatically prefix ‘in’, personally.)\n\n\n\nThis is one of a couple places where JME abused ‘enum’ when old style constants would have been better and more flexible. (Off the top of my head, blend mode was another one.)",
  "title": "AI created changes, should it create PR's or work on my own fork"
}