-
-
Notifications
You must be signed in to change notification settings - Fork 51
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
Query improvements #45
Conversation
6fdcd5e
to
521da1f
Compare
Codecov Report
@@ Coverage Diff @@
## master #45 +/- ##
=========================================
Coverage ? 83.25%
=========================================
Files ? 25
Lines ? 2699
Branches ? 0
=========================================
Hits ? 2247
Misses ? 452
Partials ? 0
Continue to review full report at Codecov.
|
Kinda lame that it needs to have Weird that the Windows build times out, could be due to |
The windows timeout could be because of this, I added a secret env variable in the travis project settings for codecov.io |
@johan-bjareholt You should be able to put the secret env variable in the environment field for the specific build (in the Travis config, not in the Travis UI). That way it wouldn't be used in the Windows build in the first place (although it would obviously be preferred if they just fixed the issue upstream). |
Just realized that you only needed the codecov.io token on private repositories so I removed it. We'll see if it works now... |
@ErikBjare Works now, please review |
Can I see a more complex query example using the new features (if/elif/else, ==)? I assume the if/elif/else syntax you've gone for would make query2 no longer a subset of Python syntax? Does this mean a further departure from the query2 in aw-server-python? If so, that should be documented somehow (or the new features at least clearly marked unstable). |
The tests has lots of examples on all of that with multiple variations.
It has never really been a subset of python, it's just that the syntax has been so simple that it might look like python but it could've just as well have been javascript or some other scripting language which uses normal +-/*% operators, = for assigning variables without a type declaration, calls funtions with parentheses and supports lists and hashmaps with {} and []. The reason for using {} instead of : and space indentation like in python is because that space indentation would be pretty annoying to parse and space indentation doesn't have any technical advantages.
We're still backwards compatible. The day query2 in aw-server-python is dropped we can start using the new query features in the web-ui but for now we shouldn't. |
@ErikBjare Can I merge this? |
10a6ef0
to
80484aa
Compare
@ErikBjare Pls review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven't looked at it carefully but looks good to me.
Additions:
Issues:
Fixes #44
Fixes #39