unhelpful error messages

[maxcan]

When calling tsoa swagger or tsoa routes:

node_modules/.bin/tsoa routes

Options:
  --help, -h           Show help  [boolean]
  --configuration, -c  tsoa configuration file; default is tsoa.json in the working directory  [string]

Cannot read property 'toLowerCase' of undefined

users.ts:

import {Get, Route, Post} from 'tsoa'
import * as Models from "../models"
import { getCxn } from "../db-util"
import * as Api from "../api-common"

export interface LoginArgs {
    email: string
     token: string
}
@Route('Users')
export class UsersController {
    @Post()
    public async createUser(email: string, token:string): Promise<Api.User> {
      return {} as Promise<Api.User>
//        return await getCxn().then(Models.loginUser(email, token, "DevManual"))
    }
}

api-common.d.ts:

export type AuthSource = "Cognito" | "Facebook" | "DevManual"

export interface DayPlan {
    title: string
}

export interface UserAuth {
    id: number
    token: string
    source: AuthSource
}

export interface User {
    email: string; days: DayPlan[]
}

tsoa.json:

{
    "swagger": {
        "outputDirectory": "./dist",
        "entryFile": "./src/controllers/users.ts",
        "basePath": "/v1",
        "name": "macrofit",
        "description": "macrofit"
    },
    "routes": {
        "basePath": "/api/v1",
        "entryFile": "./src/controllers/users.ts",
        "routesDir": "./src"
    }
}```

[lukeautry]

@maxcan I think this should be fixed with your PR, live in 1.0.11.

[maxcan]

Well I still think full stack traces and more debugging information would be extremely Helpful

…

On Mon, Jan 9, 2017 at 14:56 Luke ***@***.***> wrote: @maxcan <https://github.com/maxcan> I think this should be fixed with your PR, live in 1.0.11. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#39 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAneTMRxRESMCjzU7A6t_8GMiKoSiSzHks5rQrsVgaJpZM4Lc77N> .

[lukeautry]

Yeah, stacktrace would definitely be useful. I'll look into it.

[maxcan]

stack traces would be an easy win.

a big, but a bit harder win, would be if the errors could log the type that was being processed that caused the error.

[lukeautry]

@maxcan The errors should be a lot better as of 1.0.19.

In addition to stack traces, there's also a log error telling you what the type was when the error occurred; should make tracking down this stuff much easier.

Thanks for the feedback.

[maxcan]

👍

…

On Sat, Feb 11, 2017 at 08:56 Luke ***@***.***> wrote: @maxcan <https://github.com/maxcan> The errors should be a lot better as of 1.0.19. In addition to stack traces, there's also a log error telling you what the type was when the error occurred; should make tracking down this stuff much easier. Thanks for the feedback. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#39 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAneTGkVFBbvfgJUve2u9djJ3vGzArg4ks5rbehagaJpZM4Lc77N> .