Skip to content

Conversation

@Yogeb-tech
Copy link
Contributor

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:

  • groupParens()
  • ungroupText()
  • joinAdjacentOthers()
  • makeSubgroup()
  • findICN()
  • reqIsThrowaway()

@mikehquan19
Copy link
Contributor

@Yogeb-tech Great attempt since requisite parser is literally the most complicated thing API team has ever created. I will look into it soon.

@mikehquan19 mikehquan19 self-requested a review January 14, 2026 18:18
@Yogeb-tech
Copy link
Contributor Author

Yogeb-tech commented Jan 14, 2026

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.

@Yogeb-tech Yogeb-tech changed the title Issue #42 - Add unit tests for api-tools/parser/section/requisiteParser [In-Progress] Issue #42 - Add unit tests for api-tools/parser/section/requisiteParser [Finished!] Jan 27, 2026
@Yogeb-tech Yogeb-tech marked this pull request as ready for review January 27, 2026 07:43
@Yogeb-tech
Copy link
Contributor Author

Yogeb-tech commented Jan 27, 2026

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants