v9 KubeOps Generator cant handle separate projects?

[ewassef]

We have always carved out our entities into a separate project and distributed them via Nuget for other projects to be able to create CRDs as needed, however, it seems that with the new codegen in the KubeOps.Generator class, it will fail to detect the entities (and everything else) if its only referenced in the operator (aspnet) project. But the weirder thing is that it will create multiple default classes in each of the referenced projects (creating duplicate methods and failing to compile) if its referenced in the entities project.

Is this the desired behavior? whats the intent for the code generators? just to avoid reflection on startup?

[ewassef]

@buehler , run into this before?

[buehler]

Hey @ewassef

Not until now :)

The generator only creates convenience methods for entities. As such, there should not be any problems. Maybe I misconfigured the generator? Was the first time I wrote a c# source generator.

[ewassef]

I've never done it either :)
But I'm thinking that it might be as quick as adding a unique identifier to the filename.

context.AddSource(
            $"EntityDefinitions.{Guid.NewGuid()}.g.cs",
            SourceText.From(declaration.ToString(), Encoding.UTF8, SourceHashAlgorithm.Sha256));

Ill try it out and lyk

[ewassef]

looks like that would work #758

[buehler]

Hmm :-) nice

And the generator does not create conflicts with this? I thought that if new files are added, old ones may conflict.

[ewassef]

mmm. interesting.. ill test that specifically.. the tests that are there ran fine and didn't seem to mind