Skip to content
This repository has been archived by the owner on Oct 5, 2020. It is now read-only.

forward-compatibility with angular 2 #357

Open
joemfb opened this issue Jun 9, 2016 · 3 comments · May be fixed by #367
Open

forward-compatibility with angular 2 #357

joemfb opened this issue Jun 9, 2016 · 3 comments · May be fixed by #367

Comments

@joemfb
Copy link
Contributor

joemfb commented Jun 9, 2016

we should start porting directives to components (including the "Community Add-ons"), for forward-compatibility with angular 2. The angular-component polyfill brings support back to angular 1.3.

@Audarth
Copy link
Contributor

Audarth commented Jun 14, 2016

https://github.com/toddmotto/angular-styleguide has a lot of good info for this!

@grtjn
Copy link
Contributor

grtjn commented Jun 14, 2016

We could take the opportunity to improve the code base a little further in general. Some controllers are interacting with the backend in a fairly direct way. Would be nice if we would go through services for that. So in create and detail ctrl you'd do something like docManager.create and docManager.get, instead of making calls to mlRest directly..

@grtjn
Copy link
Contributor

grtjn commented Jun 25, 2016

I like the angular-styleguide. It would be good though if we could find a tool that could validate those guidelines to both help the transition, and to make sure we keep conforming in future..

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

Successfully merging a pull request may close this issue.

3 participants