OpenAPITools / OpenAPITools/openapi-generator
[REQ] Deprecating Unreal Engine 4 support
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
Is your feature request related to a problem? Please describe.
I am the original author and maintainer of the cpp-ue4 template.
For maintenance purposes, i'd like to deprecate Unreal 4 support and focus only on forward compatible Unreal 5 support.
Describe the solution you'd like
There are several ways to approach this and I'd want the opinion and approval of the maintainers of openapi-generator to move forward.
- Create a new template cpp-ue5, and deprecate cpp-ue4. I will no longer maintain cpp-ue4
- Add a new template cpp-ue, with explicit guarantees of compatibility with Unreal Engine versions. How far back do we want such compatibility?
- Keep maintaining both in cpp-ue4, however the complexity and areas that require polyfill will keep increasing. The generated code is also less readable.
- Create an option in the generator and try to resolve these conflicts by picking different mustache files or switching on the unreal engine version. This is also a viable and elegant way to deal with the issue, but the generator name is still cpp-ue4
Additional context
On average, Unreal releases 3 major versions per year. Unreal themselves on their marketplace only support the latest version and 3 version back for code plugins. I think a year of support is reasonable in this case.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the cpp-ue4 template and the 13-comment discussion. Compare the four proposed approaches—cpp-ue5, cpp-ue, continued dual support, or a generator option—and determine which path maintainers approve. Done means an agreed compatibility and deprecation plan is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, unreal-engine
- Domain
- game-dev, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100