René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"New configuration concept: \"presets\"","articleBody":"## Problem\n\nAs we build new functionality into `oapi-codegen`, there are new features which should become the defaults, because they provide a much better experience.\n\nFor instance, [using the new `nullable` support](https://github.com/oapi-codegen/oapi-codegen?tab=readme-ov-file#generating-nullable-types), but there are other features that are opt-in, such as those we are looking at making in [the 3.x release](https://github.com/oapi-codegen/oapi-codegen/issues?q=is%3Aissue%20state%3Aopen%20milestone%3Av3.0.0).\n\nHowever, [we try to avoid changing the generated code](https://github.com/oapi-codegen/oapi-codegen/blob/main/CONTRIBUTING.md#making-changes-that-tweak-generated-code) for new features, and only plan to change the existing templated code if strictly necessary (i.e. to fix a bug).\n\nSo in this case, there's no handy way to \"nudge\" users to use the new functionality, aside from them having to read the docs and opt-in.\n\nWaiting until 3.x (which will come with a slew of other breaking changes) is unlikely to be a good idea, especially as we have no idea when that will be (as noted in https://github.com/oapi-codegen/oapi-codegen/discussions/1606)\n\nHowever, we don't want to rely on users needing to do as much to get a better experience.\n\n## Solution\n\nInstead, we should _shamelessly_ take inspiration from [Renovate's presets](https://docs.renovatebot.com/key-concepts/presets/) and introduce a means for users to take pre-configured set of defaults (separate to the actual defaults when using `oapi-codegen` with minimal configuration)\n\nThese will have a slightly different approach for stability, where generated changes will be possible, due to it having a slightly different behaviour to the \"normal\" defaults.\n\nWe should also define the \"preset ladder\", to indicate when a feature could be promoted to a \"recommended\" option.\n\nInitial thoughts would be that a configuration item cannot enter the presets until at least 1 minor release later.\n\n## Out of scope\n\nIt will not be possible to create your own presets.\n\nThere will only be one preset, `config:recommended`.\n\nIt will be possible to use multiple presets (as an array format) but it will only be allowed to be a singleton, pending further decision on behaviour.\n\n","author":{"url":"https://github.com/jamietanna","@type":"Person","name":"jamietanna"},"datePublished":"2025-03-06T21:12:02Z","url":"https://github.com/oapi-codegen/oapi-codegen/issues/1920"}