Simon Schmid

I remember having this once, too. I closed Unity and Rider and resetted my project with ```sh git clean -ffdx ``` This helped in my case!

I have updates on this that you can follow here #1005 Will close this issue in favour of #1005

Hi! I will close this in favour if #1005 which is about the new code generator that properly supports namespace and multiple projects, like when using Unity asmdef.

I haven't forgotten about this ancient issue :D We might finally get there soon with the new code generator #1005

Hello! While working on the new code generator that uses C# `IIncrementalGenerator` I remembered this issue and implemented it. https://github.com/sschmid/Entitas/issues/1005#issuecomment-1600583297 Unfortunately, very shortly after I decided to remove it again....

Re-opened, I might reconsider and add it

I think that's something the component author can implement and should not be generated by default, e.g. ```csharp public sealed class MyComponent : IComponent { public float Value1; public int...

Unity meta files should persist, so the "unity package builder repo" would potentially contain all projects, right? Every release will result in additional commits to persist meta file changes which...

Hi! I'm thinking of this: ```csharp namespace MyFeature { [Context(typeof(MainContext))] public sealed class PositionComponent : IComponent { public int X; public int Y; } } ``` Will result in: ```csharp...

The first step would be just changes in the generated code which doesn't require any api changes in Entitas. Next step would be to move Entitas itself to nullables, which...