Ed Ball
Ed Ball
It would be great if the library could deserialize into properties of the following interfaces: * [`IReadOnlyCollection`](https://msdn.microsoft.com/en-us/library/hh881542(v=vs.110).aspx) * [`IReadOnlyList`](https://msdn.microsoft.com/en-us/library/hh192385(v=vs.110).aspx) * [`IReadOnlyDictionary`](https://msdn.microsoft.com/en-us/library/hh136548(v=vs.110).aspx)
If we want to support linking to other kinds of external documentation, we could add a `Format` property. For example, `msdocs` could conform to the docs.microsoft.com pattern, e.g. https://docs.microsoft.com/en-us/dotnet/api/system.datetime. We...
We currently just support "same repository" but a `Url` property could point to an entirely different repository.
A single configuration item could support an array of `namespaces`.
When finding external documentation configuration, we should match descendant namespaces. If there are multiple matches, we should use the longest match.
Only documented when `--visibility private`, they are currently documented with non-static constructors, but they probably deserve their own page.
There's one directory per namespace, and we should clean them all. Since the codegen comment we look for includes the assembly file name, it should be safe to clean all...
The `DAPPER` preprocessor directive guards some code that tested Dapper, but we aren't currently running those tests.
Apparently Android apps can't access the system-installed sqlite, so the Android tests currently fail.