-
Notifications
You must be signed in to change notification settings - Fork 248
[Q] Should with support the filter syntax |filter(arg1, arg2)
#772
Comments
Two 👍 for option 2. IMHO, AngularDart should match Dart syntax and semantics to every extent possible. (And the influence is two way: e.g., as you already know, that is why I asked for function pipes to be added to Dart.) |
…and methods Closes dart-archive#359, dart-archive#394, dart-archive#397, dart-archive#757. Relates to dart-archive#772, dart-archive#773.
… to observe lists and maps Closes dart-archive#359, dart-archive#394, dart-archive#397, dart-archive#757. Relates to dart-archive#772, dart-archive#773.
👍 option 2 (for me this is call/parameter list syntax for any C like language (I have no idea what Django/Smarty/Jinja/Twig are) |
… to observe lists and maps Closes dart-archive#359, dart-archive#394, dart-archive#397, dart-archive#757. Relates to dart-archive#772, dart-archive#773.
This still in the works? |
After having discussed with @mhevery, the status is that the current syntax is fine unless an other one would have obvious benefits |
For ref, polymer does support |
Great! Again, I vote for this in Angular too. |
I vote for this too. |
here is a similar discussion going on googlearchive/polymer-expressions#32 |
@zoechi, the link you provided doesn't work for me. |
@chalin sorry for that! I updated the link. |
See the discussion in #758. I'm creating the issue as the PR should be closed soon.
TL;DR:
|filter:arg1:arg2
and comes from Django & Smarty,|filter(arg1, arg2)
comes from Jinja & TwigThe proposed syntax should allow for named arguments as well.
If we go for the second syntax and support named arguments, the current syntax should probably be dropped.
Thoughts ?
The text was updated successfully, but these errors were encountered: