Roadmap

[lathonez]

Open:

• investigate using ripple-emulator for e2e
• release to app store(s) with travis
• map page
• graphs / charts page
• code documentation

Closed:

• implement ngrx
• implement HMR
• dynamic theming
• sonar qube analysis
• e2e coverage
• linting
• testing with watches
• Remove module loader dependency and requirement for wrapping tests in main
• 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
• e2e testing with protractor
• upgrade travis to trusty / containerised
• remove app.stub.js
• unit test Ionic Pages using Angular2 DI
• centralise Testing DI Boilerplate
• integrate with appveyor

To propose a feature for the roadmap please raise an enhancement issue!

[lathonez]

@marcmeans - FYI

[lathonez]

Linting

tslint should work out of the box if you have a tslint.json. If you would like further enhancements to linting please raise an issue and explain there.

[lathonez]

Testing with watches

Was implemented in #19. Explained in the blog and readme. If you would like further enhancements to this please raise an issue and explain there.

[lathonez]

examples of tests mocking observables/promises

I don't want this repo to turn into a "how to unit test" thing. It's a rabbit hole and I don't have the time or inclination to support it.

That being said there are certain things that I think are worth including, for example, testing Ionic @Pages using angular2 dependency injection, which is not done yet - though components are.

The best place for general unit testing questions probably stack overflow. There is an example with promises in clickers.spec.ts (most of the complex examples are therein).

[lathonez]

put example code in module structure for easy removal and showing pattern

@marcmeans - sounds interesting, but I don't know what you mean? Maybe raise an issue with some explanation?

[geoHeil]

What about Hot Module Replacement?

[lathonez]

@geoHeil are you suggesting a move back to webpack (wouldn't happen unless Ionic went back again), or using browserify-hmr?

or something else?

[geoHeil]

Not sure about implementation details, just saying HMR would be cool. As such browserify-hmr seems to be fine.

[lathonez]

just saying HMR would be cool

agreed

[ddellamico]

In this post, seems Ionic team are migrating again from Browserify to Webpack 2 to take advantage of "tree shaking." .. It would be nice start moving this project to webpack.. what do you think ?

[lathonez]

Yeah, if they do end up going with webpack2 in beta12 we'll switch over as
part of incorporating that upgrade into this repo.

I don't think it's worth doing ahead of time.

On 13 Aug 2016 02:44, "Damien" notifications@github.com wrote:

In this post http://blog.ionic.io/announcing-ionic-2-beta-11/, seems
Ionic team are migrating again from Browserify to Webpack 2 to take
advantage of "tree shaking." .. It would be nice start moving this project
to webpack.. what do you think ?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#38 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AG5tSHHF88L9uMX8Eu6Btm0xCshvzM79ks5qfKLUgaJpZM4Hsebj
.