-
Notifications
You must be signed in to change notification settings - Fork 43
Issue #42 - Add unit tests for api-tools/parser/section/requisiteParser [Finished!] #116
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
base: develop
Are you sure you want to change the base?
Conversation
|
@Yogeb-tech Great attempt since requisite parser is literally the most complicated thing API team has ever created. I will look into it soon. |
|
Thank you! By the way I sent a DM with questions about the issue. I have some questions I would like to ask before going further. |
|
OK, I think everything looks good, I didn't have to modify any external files. Additionally, I would like to ask when we are getting started on GraphQL because it sounds pretty interesting. I don't really want to pick up another issue unless its pretty far away. |
|
@Yogeb-tech Sweet, this is important test so it will take some time to finish. As for graphQL, I sort of push it back to the later half of the semester, you can always work on it as long as you are interested. Later half of the semester mostly is used for finalizing and stuff. |
Getting started on the task, let me know if you have any suggestions or concerns as I implement stuff.
Here are the core functions I plan to test in the requisite parser: