test: test searchOrganization() query parser#89
Merged
Jonathan-Zollinger merged 3 commits into0.1.0from Mar 23, 2026
Merged
Conversation
Signed-off-by: jonathan zollinger <jonathan.zollinger@gmail.com>
Signed-off-by: jonathan zollinger <jonathan.zollinger@gmail.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Since searchOrganization() has no conditional parameters that only need to be used if other parameters are not used it does not require any enums to be written for it. Therefore I simply added basic tests for the query parser searchOrganizations().
A few things to note about this is that I chose not to find out why the min and max length headers do not actually prevent a string with too few characters from being entered and sent in the query.
Additionally adding specifications into the schema that the two parameters should not be left as null fails to be included in the compiled code.
For now I have added documentation to those two fields, so when the backend throws an exception for either of these two failures if a user looks at the documentation they can find out why.
This PR would resolve #83