Tom Longhurst
Tom Longhurst
@ArkaHnat honestly I just think this makes it more confusing. It makes sense for a module to declare what it depends on, so it knows not to start before others....
I've just managed to replicate it. - I pull main - Someone else commits and pushes to main - I commit and push to main, but don't have the latest...
I've tried ignoring those commits and now I'm getting a brand new error: ``` INFO [24-09-06 16:46:10:80] -< End: Fetching the base versions for version calculation... (Took: 7,416.53ms) >- ERROR...
Is there an ETA or plan on the fix of this? I've got auto-merged dependency updates in my repos, and if two automatically merge without rebasing in between it breaks...
Can we re-open this? I know you say pull requests welcome but I don't have enough knowledge on how the algorithms or what-not work to generate everything, otherwise I'd try...
@kant2002 I'm sorry that you have to make changes but it's a different framework so it's expected to have API differences. I didn't set out to copy the xUnit API...
> Hi, > > I really like what I have seen until now from TUnit and would like to convert our XUnit tests to TUnit. I use a lot IsType...
What is the latest on this? I don't want to mimic the xUnit API, so the options are: - manually migrate even with the pain points - develop an analyzer...
> I think, it would be good to separate the TUnit test framework and the assertions in two separate libraries, e.g. > > * `TUnit.Framework` contains the testing infrastructure, but...