ember.js - Upgrading coupled Ember & Laravel projects (same folder) -


i working on project using old software front-end , back-end frameworks.

front-end: ember 1.8 , back-end: laravel 4.2.

ember needs 2.5 , laravel needs 5.2.

i have seen laravelshift website upgrading end prefer use due saving time.

now web application setup laravel , ember within same directory.. ember folders reside in directory called 'client' , laravel files residing under 'app'.

i have tried upgrade ember without de-coupling projects , failed numerous times, getting errors in terminal complaining parsing json files - (referring package.json / bower.json).

what proper way done? have search each dependency individually on github , see if compatible newer ember version , install manually?

up till have used: http://emberigniter.com/update-latest-ember-data-cli/ , couple of other guides , haven't made progress.

i using gulp task runner, when run compile project spits out error:

/users/jcharnock/desktop/newatp/pt2/build/js-common.js:27 var emberbuild = path.resolve(pkg.browser.ember);                                          ^  typeerror: cannot read property 'ember' of undefined     @ object.<anonymous> (/users/jcharnock/desktop/newatp/pt2/build/js-common.js:27:42)     @ module._compile (module.js:409:26)     @ object.module._extensions..js (module.js:416:10)     @ module.load (module.js:343:32)     @ function.module._load (module.js:300:12)     @ module.require (module.js:353:17)     @ require (internal/module.js:12:17)     @ /users/jcharnock/desktop/newatp/pt2/gulpfile.js:31:11     @ array.foreach (native)     @ object.<anonymous> (/users/jcharnock/desktop/newatp/pt2/gulpfile.js:25:28)

does have experience tedious tasks this? point in right direction nice.

to speak ember part, recommend move ember-cli. i've done such jump recently, , honest, lot of work!

generally should try jump ember 1.13 first if possible, , jump on 2.0 mark. because if have running on 1.13 without deprecations run under 2.x!

so best order:

  • first move ember 1.13, disable depends on other plugins
  • then move ember-cli
  • then jump ember 2.x
  • rebuild plugin stuff

the other way go, , did start new ember-cli application , integrate old code file file. better solution if have change lot, , if move es6 modules will have touch each file.

the downside won't nice deprecations 1.13, app might stop working. can't hole app, have file file. me week sitting down , doing it, transferring component, test it, fix it, next.

its big jump. luck.


Comments

Post a Comment

Popular posts from this blog

jOOQ update returning clause with Oracle -

according http://www.jooq.org/doc/3.8/manual/sql-building/sql-statements/update-statement/ jooq doesn't support returning clause in update statements databases except firebird , postgres. does know, still correct oracle jooq? according oracle's documentation, oracle db supports returning clase delete, insert, or update statements. incorrect manual you're right - manual wrong , should fixed: https://github.com/jooq/jooq/issues/5470 single row update returning jooq 3.8 added support single row update .. returning statements. internally, uses callablestatement , pl/sql block of form: begin update "my_table" set "my_table"."column" = 'xyz' "my_table"."id" = 1 returning "my_table"."id", "my_table"."column" ?, ?; ? := sql%rowcount; end; the relevant issue is: https://github.com/jooq/jooq/issues/5190 multi row update returning a...
Read more

java - Warning equals/hashCode on @Data annotation lombok with inheritance -

i have entity inherits other. on other hand, i'm using lombok project reduce boilerplate code, put @data annotation. annotation @data inheritance produces next warning: generating equals/hashcode implementation without call superclass, though class not extend java.lang.object. if intentional, add '@equalsandhashcode(callsuper=false)' type. is advisable add annotation @equalsandhashcode (callsuper = true) or @equalsandhashcode (callsuper = false) ? if not added, 1 callsuper=false or callsuper=true ? the default value false . 1 if don't specify , ignore warning. yes, recommended add @equalsandhashcode annotation on @data annotated classes extend else object. cannot tell if need true or false , depends on class hierarchy, , need examined on case-by-case basis. however, project or package, can configure in lombok.config call super methods if not direct subclass of object. lombok.equalsandhashcode.callsuper = call for configuration system ...
Read more

java - BasicPathUsageException: Cannot join to attribute of basic type -

i using java 8 jpa (hibernate 5.2.1). have clause works perfectly, until introduce clause make use foreign key table values too. i getting following error: basicpathusageexception: cannot join attribute of basic type i think problem related fact have join table, , not sure how create join using join table. employee - employee_category - category model (employee.java): @manytomany(cascade = cascadetype.all, fetch=fetchtype.eager) @jointable ( name="employee_category", joincolumns={ @joincolumn(name="emp_id", referencedcolumnname="id") }, inversejoincolumns={ @joincolumn(name="cat_id", referencedcolumnname="id") } ) private set<category> categories; model (category.java): @id private string id; jpa when introduce following code, fails error above (i think problem new piece of code): join<t, category> category = from.join("id"); predicates.add(criteriabuilder.like(category....
Read more