-
Notifications
You must be signed in to change notification settings - Fork 6.7k
Component prefixing #4373
Comments
About the |
I don't think we should remove the |
I have seen that before, but I'm speaking of the reality of the ecosystem. It can be found in third party libraries all over the place. |
That doesn't mean it is done correctly. Personally I don't like them, adds nothing. But I don't mind leaving them anyway. |
@BobbieBarker @wesleycho My schedule is getting back to normal, I can tackle Datepicker and Typeahead if you haven't started these yet. Sorry, I should have looked at PR's! Will take a look at #4509 tests. |
@RobJacobs There is a PR for datepicker but @wesleycho tried to do a bit too much with it and well, it is more stuck. Typeahead is almost done I think. |
If you want to fix the tests in my attempt at the datepicker one, you're more than welcome to :) . |
So this is the proposal for the prefixing.
Steps for a
foo
component:foo.js
, copy all the content of the file below that comment (removing modules dependencies in here so it is aget
module instead ofcreate
).$watch
using the old directive name)value
service in the module after the comment to suppress the deprecation warnings.if
inside the deprecated directives to log the deprecation.foo.spec.js
and below that, a new describe to check that the suppression works.For the commit title, it is more a feature than a bug fix (It features a prefix now).
Here is the list in strict order (some component depend on other components). If you want to tackle one, edit this to add yourself.
Important: If there is any $ in a service / controller / directive, remove it.
The text was updated successfully, but these errors were encountered: