-
Notifications
You must be signed in to change notification settings - Fork 69
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
Create workflow to check query forms #450
Comments
Hello @andrewtavis 👋🏾, well done for #451 !! |
Thanks for your offer to help, @DeleMike :) Maybe I can solve the current issues with the queries later tonight, and from there we can make some issues for the extra features? |
Sure! I will ping you later, then! |
#450 Script and workflow created for query form check
Ok @DeleMike, with #451 in we now need the following:
CC @axif0 who's also looking for Python work to do :) Do you all want to plan out the work here? |
Thanks @andrewtavis! We will look into it. @axif0 how about we break this into parts? Some questions: Also, I believe these checks will be part of our local tests, yes? |
Honestly let's keep this to expanding the And ya we really should do a single Python or shell script that runs all of the checks we've been working on locally and add a note on that into the testing section of the contriving guide 😊 |
I'm done with |
This would be great, @axif0! This can form the basis of some of the other work here. So as with getting all the form texts, we should also parse and get all forms that are being returned from the query. This first check will be to make sure that each is unique, and from there we can work towards making sure that what's being returned matches what's in the forms 😊 |
[OFF TOPIC] But hoping to come back soon and resolve this issue! They said I need rest. EDIT: I had to drop this update so that it doesn't seem I am silent. |
No stress, @DeleMike! Please take care and feel better soon! |
Thank you for the update. I hope you feel better soon! If there’s anything I can do to assist with this issue while you’re away, please let me know, and I’m happy to coordinate with @andrewtavis and @axif0 if needed. Take care! |
Get well soon @DeleMike :) Hi @andrewtavis, @DeleMike , @axif0 and @OmarAI2003 I also want to help here. Should we all do one task each? |
Ok @axif0 finished the first two :) @OmarAI2003, do you want to do the edit to this process that checks to make sure that the order of the returned forms is the same as how they appear below in the query? And @KesharwaniArpita, can you check the functions and make sure that they have the needed checks included? |
Sure @andrewtavis |
Sure, thanks, Andrew. |
@andrewtavis I am a little confused by like what functions are we talking about? The one in the |
Would be the functions in |
Thank you so much everyone! ✨ Feel a bit better :) |
Great to hear, @DeleMike! |
So last thing here is to check that the actual QIDs that make up the form after |
Yeah, and the ordering of the labels in sELECT to be based on the lexeme forms JSON. |
Yess!! |
Terms
Description
This issue is to document work that I've been doing to create a check for form identifiers within all Scribe-Data queries. The check goes through and derives the properties of all forms and create a new metadata file for lexeme forms from which a naming criteria is derived.
Contribution
I'm working on this. Current status at time of writing is that I need to add in a check for whether all forms are actually returned in the query, that each returned form is unique, and that returned forms are ordered in the same way as the metadata file. From there also a minor check to see that the query docstring is correct would be good.
From there I need to go through and rename all the forms in the queries that have issues :)
The text was updated successfully, but these errors were encountered: