More information on limitations when using production builds #3

Activity

1. jessehon

   changed the title [-]More information on limitations when using production[/-] [+]More information on limitations when using production builds[/+] on Nov 30, 2017
2. daniel-lang commented on Nov 30, 2017

   

   daniel-lang

   on Nov 30, 2017

   Contributor

   More actions

   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

   👍React with 👍1Reacted by slimlime
3. vhb56 commented on Dec 5, 2017

   

   vhb56

   on Dec 5, 2017

   More actions

   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.
4. daniel-lang commented on Dec 5, 2017

   

   daniel-lang

   on Dec 5, 2017

   Contributor

   More actions

   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.
5. azimuthdeveloper commented on Jan 4, 2018

   

   azimuthdeveloper

   on Jan 4, 2018

   More actions

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

   added

   question

   on Jan 18, 2018
7. meddario commented on Nov 6, 2018

   

   meddario

   on Nov 6, 2018

   More actions

   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!