Tsoa: Is this warning correct? *partially collides*

Created on 22 Jan 2021  路  5Comments  路  Source: lukeautry/tsoa

We have code that works perfect using tsoa 3.4.0 ( and prior) but after upgrading to 3.5.1 i get this warning and it seams to be
a bit strange. I would not expect this to be an issue. as it has worked for a long time.

Method setLocationConsent route: /locations/{locationId}] may never be invoked, because its route is partially collides with [Method enterOrLeaveLocation route: /locations/{locationId}/event]

@Post("/locations/{locationId}")
public async setLocationConsent(

@Post("/locations/{locationId}/event")
public async enterOrLeaveLocation(

Stale

Most helpful comment

We are too strict right now, this should not trigger a warning. Will be fixed in the next release

All 5 comments

I guess "locationId" could also be a string like "locationa/partB" .. and then it would be correct, not quite sure how all the frameworks handle this, as far as I remember it's not an issue with express and koa, but could be on other frameworks.

It's just a warning, maybe allow some options to "ignore" this warning?

Location Id is a string, and we use it with express, we have used this a long time and never seen a problem.
An option specifying target, to remove irrelevant warnings would be nice ;)

We are too strict right now, this should not trigger a warning. Will be fixed in the next release

Thanks

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days

Was this page helpful?
0 / 5 - 0 ratings

Related issues

williamdes picture williamdes  路  5Comments

sundowndev picture sundowndev  路  4Comments

zarubto4 picture zarubto4  路  6Comments

rdhelms picture rdhelms  路  4Comments

jeremyVignelles picture jeremyVignelles  路  3Comments