Open neoeinstein opened 8 years ago
This issue has a bit of a hiccup in that we are necessarily exporting the Json
type. Even if we didn't export any other types, all consumers of this library generally need to agree on one Json
type. If Chiron is included from multiple file sources, these Json
types won't agree (or cause compilation errors), and so this may not be something we can easily resolve in a truly Paket file-include friendly way.
Add a compiler directive
CHIRON_PUBLIC
to distinguish between the cases where Chiron is being published as a NuGet package versus as a single-file include. This same mechanism can also allow Chiron to be included once but shared within an application.