Inconsistent cases in guard functions

flowup / api-client-generator

Angular REST API client generator from Swagger YAML or JSON file with camel case settigs

MIT License

115 stars 21 forks source link

Inconsistent cases in guard functions #83

Closed warmans closed 4 years ago

warmans commented 4 years ago

Fixed issue where guard function name would be inconsistent between definition and usage in the service causing an invalid function call in generated client.

It seems the generated example clients were slightly out of date so running generate:all has made some other minor changes.

vmasek commented 4 years ago

Thank you for the PR, I'll have a look at it :+1:

vmasek commented 4 years ago

Merged, next time please use the conventional commit notation so I can leave your commits as they are for this PR it should be something like this fix(type-guards): guards name definition and usage inconsistency