Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFE: Add "Contains" operator for Expression Language #928

Closed
codenameone opened this issue Mar 27, 2015 · 4 comments
Closed

RFE: Add "Contains" operator for Expression Language #928

codenameone opened this issue Mar 27, 2015 · 4 comments

Comments

@codenameone
Copy link
Collaborator

Original issue 928 created by codenameone on 2013-10-27T06:24:23.000Z:

Attached is a patch for EL that includes the following:

  1. add a new "contains" operator for the expression language, which works with both array and string nodes.

  2. bugfix: when trying to select an element from a string array, an error is thrown: java.lang.IllegalArgumentException: Syntax error: array close must be followed by a separator

The bug and use case for new feature are documented in the forum at:

http://www.codenameone.com/discussion-forum.html?place=msg%2Fcodenameone-discussions%2FNnVSd6KSj9o%2F_z3clJshx7YJ

@codenameone
Copy link
Collaborator Author

Comment #1 originally posted by codenameone on 2013-10-27T19:23:54.000Z:

This refers to StringTokenizer.
Can you please submit the files themselves, it would be easier than patch files.
Thanks.

@codenameone
Copy link
Collaborator Author

Comment #2 originally posted by codenameone on 2013-10-27T19:36:35.000Z:

Sure. Is StringTokenizer a problem? I can revise to use StringUtil if needed.

@codenameone
Copy link
Collaborator Author

Comment #3 originally posted by codenameone on 2013-10-27T19:45:51.000Z:

Sources in place of patch (revised to remove StringTokenizer)

@codenameone
Copy link
Collaborator Author

Comment #4 originally posted by codenameone on 2013-10-28T06:22:13.000Z:

Thanks, that's committed to SVN.
StringTokenizer isn't currently available in the supported subset.

@codenameone codenameone removed their assignment Jul 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants