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.

Sign up for GitHub

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

Jump to bottom

support in operator in searches #34

Closed
mfrasca opened this issue Jan 26, 2016 · 1 comment
Closed

support in operator in searches #34

mfrasca opened this issue Jan 26, 2016 · 1 comment
Labels
ux ux bug

Comments

@mfrasca
Copy link
Member

mfrasca commented Jan 26, 2016

plant where id in [1,2,3]
is not currently supported.
it would be practical to complete the functionality of the :tags screen described in #27
@mfrasca mfrasca added the ux ux bug label Jan 26, 2016
@mfrasca
Copy link
Member Author

mfrasca commented Jan 26, 2016

without brackets: if you use the in operator, the remainder is a list.
works with non-empty lists, which does not look like a limitation to me, but we will see.

mfrasca added a commit that referenced this issue Jan 26, 2016
@mfrasca
implementing the in operator for non-empty lists.
0e41fc7 
closes #34.
@mfrasca mfrasca closed this as completed Jan 26, 2016
@mfrasca mfrasca mentioned this issue Jan 26, 2016
Merged
mfrasca added a commit that referenced this issue Jan 26, 2016
@mfrasca
implementing the in operator for non-empty lists.
ca90128 
closes #34.
RoDuth pushed a commit to RoDuth/ghini.desktop that referenced this issue Dec 30, 2017
Merge pull request Ghini#34 from mfrasca/master
1b7f8f8 
Merge pull request Ghini#94 from Bauble/master
RoDuth pushed a commit to RoDuth/ghini.desktop that referenced this issue Dec 30, 2017
@mfrasca
implementing the in operator for non-empty lists.
bd59dda 
closes Ghini#34.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
ux ux bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mfrasca