-
Notifications
You must be signed in to change notification settings - Fork 217
Improvements to skeleton query flow #2256
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
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
89b148b to
70523b2
Compare
67d384b to
3b736aa
Compare
c00240a to
0253b5d
Compare
3b736aa to
4f294a4
Compare
0253b5d to
7d28e61
Compare
4f294a4 to
be267b1
Compare
7d28e61 to
2f70963
Compare
be267b1 to
15600cb
Compare
0545eb5 to
699c362
Compare
eefe804 to
a07b11c
Compare
699c362 to
f61440d
Compare
a07b11c to
91b591c
Compare
f61440d to
7691955
Compare
91b591c to
1fa3bda
Compare
fd25ba4 to
d9d1bff
Compare
koesie10
reviewed
Apr 4, 2023
e198a79 to
460da1e
Compare
d9d1bff to
c577bee
Compare
…loaded We'd like to select an existing database for our query, if on is already downloaded and matches the query language. Previously we were re-using the database if the language and name matched (e.g. the name would be `github/codeql`).
At the moment, we're always deciding which database to download for the user for an example query. We'd like to give them a chance to change the database, so here we're adding a step where we're showing the user a selection box with the suggested database pre-filled. They can choose to type in a different database before continuing the skeleton generation process.
c577bee to
919219c
Compare
Contributor
Author
|
Ok! I think this is also ready for a re-review. I've also tested manually that things still work as expected. |
92d8d83 to
6f6d0e2
Compare
6f6d0e2 to
de4afae
Compare
koesie10
approved these changes
Apr 12, 2023
Co-authored-by: Koen Vlaswinkel <[email protected]>
7414004 to
6fc6f39
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please review this PR commit-by-commit.
Follow up to #2250 where we added a wizard which will guide you through generating an example query based on the language of your choice.
The wizard would then create a skeleton QL pack and download an appropriate database for you, so that you could focus on just writing your query.
We've received some feedback on improvements for this flow:
Screen.Recording.2023-03-31.at.18.34.55.mov
Checklist
ready-for-doc-reviewlabel there.