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

More information on limitations when using production builds #3

Open
jessehon opened this issue Nov 30, 2017 · 5 comments
Open

More information on limitations when using production builds #3

jessehon opened this issue Nov 30, 2017 · 5 comments
Labels

Comments

@jessehon
Copy link

Would it be possible to get a bit more information or reasons for each of the limitations when using production builds. It might help us with debugging and potentially creating issues/PRs on typeorm to resolve them.

@jessehon jessehon changed the title More information on limitations when using production More information on limitations when using production builds Nov 30, 2017
@daniel-lang
Copy link
Contributor

Sure!

The reason for all three limitation is, that for production builds the source code is mangled with uglifyjs.

  • TypeORM can no longer generate table names from class names -> therefore you have to specify it and get a repository by string rather can class
  • Date gets translated into Object so TypeORM thinks, that the type of the column is Object rather than Date

@vhb56
Copy link

vhb56 commented Dec 5, 2017

Btw guys who develop & support Ionic are very friendly if there is some specific serious problem you can ask them for some integration maybe, i think they will help.

@daniel-lang
Copy link
Contributor

I don't think that these are Ionic specific problem. It's more a problem of webpack and the underlying build scripts that are partly from angular.

@azimuthdeveloper
Copy link

Does running a non-prod build for an Ionic app make any difference? That is, without the --prod flag.

@meddario
Copy link

meddario commented Nov 6, 2018

A question: if i use TypeORM with the active record pattern, how can i explicitly specify the table name (as suggested for repository pattern here)?

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants