-
Notifications
You must be signed in to change notification settings - Fork 198
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tsoa service doesn't work from two different entrypoint locations #6380
Comments
I think the library should require that an absolute path and add support for And we should deprecate |
You'll notice that:
Given the following:
|
Hi, This issue hasn't seen activity in 90 days. Therefore, we are marking this issue as stale for now. It will be closed after 7 days. |
I tried this:
I tried using the tsoa service from two different entrypoints (different directories).
It turns out that the folder resolution is based on the location of the entrypoint (*.main.w file)
This happened:
currently the tsoa service is dependant on the entrypoint location, which makes it impossible to work with.
I expected this:
to work the same from any place
Is there a workaround?
No response
Anything else?
No response
Wing Version
No response
Node.js Version
No response
Platform(s)
No response
Community Notes
The text was updated successfully, but these errors were encountered: