Skip to content

Conversation

ewassef
Copy link
Collaborator

@ewassef ewassef commented May 13, 2024

This will allow the different components to be separated into different projects. This can be helpful in the case where you have the entities in a different project to be published in a nuget package

This will allow the different components to be separated into different projects. This can be helpful in the case where you have the entities in a different project to be published in a nuget package
@buehler
Copy link
Collaborator

buehler commented May 13, 2024

As by my comment in #750, shouldn't the addition to the name be deterministic? like the project identifier or the project guid or something?

@ewassef ewassef closed this May 21, 2024
@ewassef
Copy link
Collaborator Author

ewassef commented May 21, 2024

this wont actually work.. closing

@ewassef ewassef deleted the feature/multiple-sourcegenerators branch May 21, 2024 23:31
@buehler
Copy link
Collaborator

buehler commented May 22, 2024

Hey @ewassef
What did not work? I assume the problem still persists?

@ewassef
Copy link
Collaborator Author

ewassef commented May 22, 2024

Ya the way the extension is called isn't letting me chain them from different files. Also, if the entities are referenced externally, the source generator doesn't look at the referenced assembly symbols (and even if it did, can't get the class declaration needed for the entities array) so it will always generate empty files.

It will likely be some deeper thought but the simplistic approach I thought it needed didn't work

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants