Open Eclegv opened 2 months ago
We'll update "Blueprint41.Build" to translate the slashes and back-slashes to the correct path separators for the platform where it's running. That way it doesn't depend on anyone accidentally defining the target path using the right separator slashes.
Kind of issue
In which operating systems have you tested?
Hello !
I was setting up a github action for my dotnet project using blueprint41 and, while trying to run I encountered a problem with the Blueprint41.Build.Json.
How to fix it
To fit it, I had to modify the generatePath field from "..\Entities.Generated" -> "..//Entities.Generated". Doing so doesn't cause any problems on windows, where I'm developing.