Thanks , but that’s a little different to what I was referring to. In my plugin code, I now need to specify, as an example:
#include "Widgets/Text/TextBlock.h"
when previously the following would have sufficed (due to having “Slate” in my module’s PublicDependencyModuleNames list):
#include "TextBlock.h"
This extends beyond engine dependencies, to cross plugin dependencies and even intra-plugin module dependencies. I have to specify the full relative path (from “Public/”) when including a header from MyPluginModuleA into a file in MyPluginModuleB. It’s no big deal, I actually think it’s better this way. I was just checking whether this change was intended for plugins, since it has not been forced on game project code.