Incorrect formatting of #include statements in new code class added to project that is not properly set up for IWYU

Attempting to add a new code class to a project that is not correctly set up for IWYU (such as an older project that may not have been properly modified for IWYU when upgrading) will result in the build of the project with the new class failing. The build fails because the .cpp file for the new code class is created with two #include statements on a single line.

REGRESSION:
No. The same behavior occurs in 4.20.3.

1. Download the attached project (created in Main CL 4594480).
   • A new code project can be used instead by commenting out the PCHUsage line in the project's Build.cs file and adding an include for the project's .h file to each .cpp file in the project.
2. Associate the project with your version of Main.
3. Build the project in Visual Studio.
4. Open the project in the Editor.
5. Add a new code class to the project.

RESULT:
The new code class will be added to the project, but the hot reload of the project with the new class will fail.

EXPECTED:
The new code class is added to the project, and the hot reload completes successfully.

Fix UE-51650

[UE-23848] Bug Status

UE-81742 DXGI_ERROR_INVALID_CALL

I am not able to find world outliner how to enable it?

Undefined sysmbol: typeinfo for AActor when cross-compile linux dedicated server on windows

How can i modify the param name in EQS node

Bonjour j'ai un petit problème c'est que je ne vois plus l'onglet "scability" pour changer les graphismes de uefn et j'ai pas trouvé l'option pour le faire revenir ?

Delay nodes occasionally don't fire the "Completed" output in a nativized build

Error UE5 5.0.3

How to convert the datasmith scene file to BluePrint. Create animations in BluePrint.