Skip to content
This repository was archived by the owner on Feb 22, 2018. It is now read-only.

Why we used some deprecated annotations of 0.10.0 angular.dart #929

Closed
smallg opened this issue Apr 18, 2014 · 8 comments
Closed

Why we used some deprecated annotations of 0.10.0 angular.dart #929

smallg opened this issue Apr 18, 2014 · 8 comments

Comments

@smallg
Copy link

smallg commented Apr 18, 2014

I upgrade angular.dart version to 0.10.0.
I found Controller, NgAttr and other annotations is deprecated.
Also it used in application.
Why we do this?

@vicb
Copy link
Contributor

vicb commented Apr 18, 2014

Because those will be deprecated in 1.0.

We should use @deprecated(msg) rather than @deprecated(), @mhevery ?

@smallg
Copy link
Author

smallg commented Apr 18, 2014

Thank you for your explanation.

@smallg smallg closed this as completed Apr 18, 2014
@zoechi
Copy link
Contributor

zoechi commented Apr 19, 2014

Any information about why? Is there already something that can/should be used instead?
http://stackoverflow.com/questions/23150818
http://stackoverflow.com/questions/23169711

@vicb
Copy link
Contributor

vicb commented Apr 19, 2014

Some info in #919 and some preceding issues.

@zoechi
Copy link
Contributor

zoechi commented Apr 19, 2014

Thanks for the hint. I saw the issue but I'm not sure if I understand the implications.
I'll add my question there.

@stiofand
Copy link

stiofand commented Jun 3, 2014

I left a question there, I can't see, to see any explanation or example of the work around, none of the documentation or official tutorials have been updated and searching forums simply brings back the same questions, is there anywhere that shows how to now annotate a controller class to the module?

@vicb
Copy link
Contributor

vicb commented Jun 3, 2014

@stevematdavies we'll publish more docs when the corresponding PRs are released. You'll only be able to have a root controller. Find the rationale and how-to in the issue you have commented.

@stiofand
Copy link

stiofand commented Jun 3, 2014

The rationale is sound to me, no concerns there, however, as for a how to, I'm still looking for one that is clearly given, hence my questions

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

No branches or pull requests

4 participants