-
Notifications
You must be signed in to change notification settings - Fork 1
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
More streamlined syntax for path expressions #9
Comments
By Istvan Rath on May 20, 2013 04:33 I'm moving these issues to the 0.8.x series as they are not essential for the 0.7 release. |
By Istvan Rath on Apr 08, 2014 18:02 Moving this feature to post-0.8. |
By Istvan Rath on Apr 24, 2014 04:25 I'm expecting this to be addressed for 0.9. |
By Abel Hegedus on Apr 19, 2016 05:25 Updating to correct milestone. |
By Zoltan Ujhelyi on Oct 04, 2017 05:26 Moving potential tasks from future to 2.0. |
By Zoltan Ujhelyi on Feb 08, 2018 07:21 Postponing to a future release. |
By Zoltan Ujhelyi on May 27, 2019 07:46 Postponing tickets to FUTURE until effort is allocated to fix them. |
| --- | --- |
| Bugzilla Link | 398788 |
| Status | NEW |
| Importance | P3 enhancement |
| Reported | Jan 22, 2013 12:13 EDT |
| Modified | May 27, 2019 07:46 EDT |
| Version | oldinquery |
| Reporter | Zoltan Ujhelyi |
Description
Cloned from: 109: More streamlined syntax for path expressions
http://github.com/ujhelyiz/EMF-IncQuery/issues/issue/109
We could have an easier syntax for path expressions. Suggestions: instead of
we could have
or even
We should discuss these.
The text was updated successfully, but these errors were encountered: