* fix NancyFX string parser
parser needs to access the Value parameter to enable the direct cast at line 102 when handling string parameters
* Updated nancyfx sample
* Added switch to config to toggle use of yaml base path as module paths
* Corrects issue #3410 when trying to create Arrays of primitive types
* Use c++11 nullptr keyword and various indentation issues resolved
* ran petstore on new mustaches
* fix NancyFX string parser
parser needs to access the Value parameter to enable the direct cast at line 102 when handling string parameters
* Updated nancyfx sample
* add configuration to typescript fetch
* fix issues reported by the CI
* fix header parameters in ts fetch client
* add new configuration file for ts fetch
* skip if check for configuration in ts fetch
* Fix `this.configuration` issue in paramsCreator
* update ts fetch samples
* Fix typescript fetch tests to work with Configuration
* Add dictionary to store apikeys (#8)
* Add dictionary to store apikeys
* Type apikey with expected params rather than Dictionary - typescript-fetch
* Update test samples to new typescript-fetch api
* Fix tests for typesript-fetch api
* update typescript sample using petstore.yaml
* added method summary under the method name
* added batch file for html2 generation on windows
* regenerated html2 example
* changed the html2 windows batch to use yaml instead of json and regenerated sample
* fixed encoding issues
* [csharp] Fix apiPackage,modelPackage,excludeTests
The apiPackage, modelPackage, and excludeTests values were not being
populated correctly from external configs (passing -c filename to
generator).
This commit allows those properties to work correctly with the Csharp
client generator. Previously the Api and Model namespaces were hard
coded after additionalProperties for these were evaluated.
The files which generate test files for models and api classes
didn't honor the excludeTests option.
* [csharp] Regenerate sample
* [csharp] Fix modelPackage in README template
This moves previous aspnet5 functionality to aspnetcore, aspnet5 now
derives from the aspnetcore generator and logs a warning that it's
deprecated.
This will help resolve any confusion because ASP.NET 5 is terminology
referring to the project of around a year ago. ASP.NET Core 1.0 is the
new name for the technology, and further enhancements should target .NET
Core 1.0 rather than any old vNext or preview stuff.
