Skip to content
This repository has been archived by the owner on Apr 12, 2024. It is now read-only.

feat($parseProvider): add the additionalIsIdent configuration method #4747

Closed
wants to merge 1 commit into from
Closed

feat($parseProvider): add the additionalIsIdent configuration method #4747

wants to merge 1 commit into from

Conversation

gurdiga
Copy link
Contributor

@gurdiga gurdiga commented Nov 1, 2013

Allows extending of the set of character allowed in identifiers used in Angular expressions.

Closes #2174 #3847

Allows extending of the set of character allowed in identifiers used in Angular expressions.
@gurdiga
Copy link
Contributor Author

gurdiga commented Nov 1, 2013

Hey guys, what do you think about this approach?

@petebacondarwin @clee704 @lhaussknecht @dipold @dmethvin

@gurdiga
Copy link
Contributor Author

gurdiga commented Nov 9, 2013

Guys, what do you think about this thread here: https://groups.google.com/forum/#!topic/angular/-BUeo-5loOQ ?

@nissoh
Copy link

nissoh commented Dec 20, 2013

in my case. it seemed to have covered all hebrew letters but it fails on hebrew letters followed by space.
מחיר לפי פקטור

@gurdiga
Copy link
Contributor Author

gurdiga commented Dec 20, 2013

Hi Nissan!

Could you please fork me and write a failing test that would illustrate you
context? I guess this would help understand the issue.

Thank you!

On Fri, Dec 20, 2013 at 9:18 PM, Nissan Hanina notifications@github.comwrote:

in my case. it seemed to have covered all hebrew letters but it fails on
hebrew letters followed by space.
מחיר לפי פקטור


Reply to this email directly or view it on GitHubhttps://github.com//pull/4747#issuecomment-31034308
.

@clee704
Copy link

clee704 commented Dec 22, 2013

The code looks good. But the name additionalIsIdent sounds a little awkward (I'm not a native English speaker, so take it with a grain of salt). Have you considered other names?

@gurdiga
Copy link
Contributor Author

gurdiga commented Dec 23, 2013

@clee704 Yeah, I agree that the name is awkward, I just picked it just because it made sense to me after digging into Angular’s internals. I will think about a name that will make sense from an API user’s perspective, and, BTW, I’m open to ideas too! ;)

@gurdiga
Copy link
Contributor Author

gurdiga commented Jan 19, 2014

@clee704 I think I might have found a good name. :)

@mercibe
Copy link

mercibe commented Feb 11, 2014

Really need this feature. Non ASCII characters allowed in identifiers sounds like a problem solved 2 decades ago ;-) Will it be merged soon? Thank you!

@Macadoshis
Copy link

Most needed feature. Please someone merge it, dammit !

@petebacondarwin
Copy link
Member

See #5881

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

Successfully merging this pull request may close these issues.

Lexer support for non-ascii literals
6 participants