Dave Thomas

These are the errors: ``` D:\a\1\s\src\Falanx.Proto.Codec.Binary\Codec.fs(28,5): error FS0010: Incomplete structured construct at or before this point in type definition [D:\a\1\s\src\Falanx.Proto.Codec.Binary\Falanx.Proto.Codec.Binary.fsproj] [D:\a\1\s\build.proj] D:\a\1\s\src\Falanx.Proto.Codec.Binary\Codec.fs(40,21): error FS0010: Unexpected symbol '=' in member definition...

@auduchinok Any ideas?

This could be a general property that could be added to all plugins or specific to the lens plugin, all plugins currently take a `namespace` property in the myriad.toml file....

Ah, lens plugin gets a namespace named `UnknownNamespace` is its empty

Same with the fields and DU's plugin, there could be a hierarchy, namespace, module, if both of those are empty then the generation occurs in the root, which might potentially...

I found an issue with generating with a module rather than a namespace. Modules can be either top-level or nested, top-level modules cannot have comments above them and are defined...

The ast has two constructs one for top-level modules, which is one per file, and another for nested modules, which are any subsequent ones. there are also anonymous modules for...

Only top-level modules can have a path like `module xxx.yyy`, nested ones are only allowed to be a simple path like `module xxx =`

Inline is probably different but there are issues with getting the indentation correctly aligned etc and knowing if you are inside a type or module or namespace already, complexity there.

tuplising things or listifying things was a plugin that aI would like to do. Such as: ``` [Myriad.tuple] myType = ... let test = myType.create ... let tupled = MyType.toTuple...