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

After choosing Postgres as the production DB the production type in orm.config.ts is set as postgresql and gives an error #70

Closed
robconnell9 opened this issue Oct 26, 2019 · 5 comments
Labels
bug Something isn't working
Milestone

Comments

@robconnell9
Copy link

Describe the bug
When there is a prompt for the production database and postgresql is chosen this populates orm.config.ts with the prod database type of postgresql at line 28. This value should be postgres as per the value in PostgresConnectioOptions.d.ts

To Reproduce
Steps to reproduce the behavior:
jhipster --blueprint nodejs
choose monolithic
choose postgresql for production database

Expected behavior
value in orm.config.ts should be postgres.

Screenshots
not required

Desktop (please complete the following information):
IOS
Chrome
current as per 26/10/19

Smartphone (please complete the following information):
NA

Additional context
Supplied as required

@ghost ghost self-assigned this Oct 26, 2019
@ghost ghost added the bug Something isn't working label Oct 26, 2019
@ghost ghost added this to the 1.0.0-alpha.4 milestone Oct 26, 2019
ghost pushed a commit that referenced this issue Oct 26, 2019
@ghost
Copy link

ghost commented Oct 26, 2019

Thanks! I have fixed that... could you try with the bugfix branch here?

@robconnell9
Copy link
Author

robconnell9 commented Oct 26, 2019 via email

@ghost
Copy link

ghost commented Oct 27, 2019

Hi @robconnell9 ,
you have to follow this steps:

These are the steps written in the CONTRIBUTING GUIDE.

As it is not the first time that are not clear (or read) these steps in that guide, I will explain that in the README.md.

@robconnell9
Copy link
Author

I followed the steps and this fixes the problem that I raised

@ghost
Copy link

ghost commented Oct 27, 2019

Good! thanks for the collaboration! You are welcome to contribute with a donation or with the development of new features, and introduce new people in this project/community :)

@ghost ghost closed this as completed Oct 27, 2019
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant