Skip to content
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

fix: coerce port to number in ConnectionOptionsEnvReader #6786

Merged
merged 1 commit into from Sep 26, 2020

Conversation

imnotjames
Copy link
Contributor

the expected type of port in all drivers is a number - and
in MSSQL this is a problem as the underlying driver does not
properly handle a string port - so we have to parseInt

closes #6781

the expected type of `port` in all drivers is a number - and
in MSSQL this is a problem as the underlying driver does not
properly handle a string port - so we have to parseInt

closes typeorm#6781
@pleerock pleerock merged commit 55fbb69 into typeorm:master Sep 26, 2020
@pleerock
Copy link
Member

Thank you!

zaro pushed a commit to zaro/typeorm that referenced this pull request Jan 12, 2021
the expected type of `port` in all drivers is a number - and
in MSSQL this is a problem as the underlying driver does not
properly handle a string port - so we have to parseInt

closes typeorm#6781
@imnotjames imnotjames deleted the fix/6781-env-port-as-number branch June 21, 2021 00:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

typeorm cli migrate:run port issue getting "config.options.port" property must be of type number.
3 participants