Put types into a namespace instead of module

[xperiandri]

Putting types into a module is not a good idea. As it causes some issues with their consumption from WPF/UWP/Uno

[Zaid-Ajaj]

Hi @xperiandri, can you tell me more about this issue? The global types are included as part of a namespace and the query-specific types are in a module inside that same namespace. What exactly needs to change / how does the expected output looks like?

[xperiandri]

You cannot instantiate nested types in XAML. For example to use as sample data to display on designer

[Zaid-Ajaj]

I see, that makes sense. Let me try to see what I can do. Unless you want to give it a try yourself 😉 PRs are always welcome

[xperiandri]

Is it fixed?

[Zaid-Ajaj]

Nope, didn't have time for it. Feel free to submit a PR for it 😄 it should be another boolean option. Maybe "nestedModuleTypes"? 🤔 where true is default, false -> generates namespaces instead

[xperiandri]

Could you point to the line where it happens?

[Zaid-Ajaj]

It happens here in the function CodeGen.generateQualifiedModule:
https://github.com/Zaid-Ajaj/Snowflaqe/blob/master/src/Program.fs#L421