Reinforced.Typings: Incorrect folder structure with .net core on macOS
Hi,
I was using RT in an ASP.NET Core app (.NET Core SDK 2.1.x). I used Jetbrains Rider IDE and everything is running on macOS.
My model is defined as:
using Reinforced.Typings.Attributes;
namespace MyAspNetApp.Models
{
[TsClass]
public class WeatherForecast
{
public string DateFormatted { get; set; }
public int TemperatureC { get; set; }
public string Summary { get; set; }
public int TemperatureF
{
get { return 32 + (int) (TemperatureC / 0.5556); }
}
}
}
In the Reinforced.Typings.setting.xml file I specified the output directory as:
<RtTargetDirectory>$(ProjectDir)MyAspNetApp\src\app\_models</RtTargetDirectory>
However, the TypeScript files get put in a weird directory structure that looks like:
. ├── … ├── src │ ├── app │ │ ├── MyAspNetApp/Models
And I was expecting: . ├── … ├── src │ ├── app │ │ ├── MyAspNetApp │ │ │ ├── Models
In other words, it outputs to a folder called ‘MyAspNetApp/Models’ instead of creating a folder ‘MyAspNetApp’ folder and placing the files in a subdirectory called ‘Models’.
I noticed this behaviour while using Jetbrains Rider and Visual Studio Code on macOS.
Any help would be appreciated.
Cheers, Psybernetic
P.S. It works perfectly when building with Visual Studio 2017 on Windows OS.
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 19 (18 by maintainers)
Commits related to this issue
- #71 > back-slashes and drive syntax hard-coded and 10 tests failing — committed to PandaWood/Reinforced.Typings by PandaWood 6 years ago
- #71 fix most mono incompatibilities — committed to PandaWood/Reinforced.Typings by PandaWood 6 years ago
- #71 fix most mono incompatibilities fix spellings in code and comments add stub to settings to prevent missing parameter error — committed to PandaWood/Reinforced.Typings by PandaWood 6 years ago
- Merge pull request #89 from PandaWood/mono-clean #71 fix some mono incompatibilities — committed to reinforced/Reinforced.Typings by pavel-b-novikov 6 years ago
Seems that original issue is fixed by @PandaWood in version 1.4.97. Please, everyone, say thanks to @PandaWood.