Paŭlo Ebermann
Paŭlo Ebermann
Reminder to me: Please finally do it!
We got several cases during the last few years where this rule would have been useful. We just should add it.
I guess this is still on hold?
Possibly the list of allowed response codes needs to be adjusted.
We now have a list of many codes in Rule [150](https://opensource.zalando.com/restful-api-guidelines/#150), and it needs some updates to the Zally rule checking this. Possibly a refactoring/re-implementation too.
We should review the list of headers (not necessarily only related to this change), and make sure only headers mentioned in the guideline are allowed.
Previous related discussion: #2318. I'm not sure why that was closed – it looks like the original issue author just modified its own templates and thus lost interest?
I think the default should be to have no timestamp. I'm not sure if there should be an option to include it. By the way, I think what could be...
@wing328 either this, or putting it into the generated README (if there is some) might be better than putting it in every file, yes.
The typescript-angular/npm examples have a date/time in the package version for NPM. Not sure how to handle that: ```json { "name": "@swagger/angular2-typescript-petstore", "version": "0.0.1-SNAPSHOT.201703251242", "description": "swagger client for @swagger/angular2-typescript-petstore", ```