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

upgrade script / checklist #30

Closed
lathonez opened this issue Mar 3, 2016 · 5 comments
Closed

upgrade script / checklist #30

lathonez opened this issue Mar 3, 2016 · 5 comments

Comments

@lathonez
Copy link
Owner

lathonez commented Mar 3, 2016

There's getting to be a lot of things to check each time ionic do an upgrade (#28). It'd be good to have a script / list of stuff to check each time.

@lathonez
Copy link
Owner Author

lathonez commented Mar 3, 2016

  • npm install -g ionic@beta
  • npm install -g ionic-app-lib
  • review changelog
  • review node_modules/ionic-angular/index.js
  • review package.json
  • review typings.json
  • review app/
  • review cordova hooks
  • take new ionic.config

@marcmeans
Copy link
Contributor

If you have a roadmap of ideas you're looking to do too, I can contribute some.

personally I'd like to see:

  • linting and testing with watches
  • typescript maps for debug/coverage
  • examples of tests mocking observables/promises
  • put example code in module structure for easy removal and showing pattern
  • build location for custom images used.

@lathonez
Copy link
Owner Author

lathonez commented Mar 6, 2016

Hey @marcmeans,

Not sure what you mean re roadmap.

The purpose of this task is to try to make sure we don't miss things when upgrading to the next Ionic version. I was thinking of scripting something up eventually, probably when the next version is out.

With regard to the wider project, Angular 2 seed have some cool stuff since I forked that I really want to implement here (#19).

After that I'll look at developing the app further as a more complete demo and releasing it in the app stores, hopefully with travis and blog posts.

Other than that it's just trying to stay on top of the Ionic changes.

If you've seen anything cool that you think would be worth putting in here raise an issue for it and we'll discuss it there.

Top of my list now is figuring out how this works. For us we have to proxy in karma.config.js too, not looked into it yet - porting the gulpfile to *.ts was prep.

@lathonez
Copy link
Owner Author

lathonez commented Mar 8, 2016

@marcmeans - I didn't see your edited comment until just now. I'll get back to you tonight.

@lathonez
Copy link
Owner Author

lathonez commented Mar 9, 2016

In the end, I think the only way of doing this at the moment is to create a new ionic starter and meld.

The advice from Ionic on this beta (3) was to move code over. So I guess you just have to meld / diff and look at all diffs.

@lathonez lathonez closed this as completed Mar 9, 2016
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

No branches or pull requests

2 participants