Skip to content
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 test scenarions #1

Conversation

otaviojava
Copy link

No description provided.

}

@Test
void shouldHandleEmptyRestrictions() {
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We might decide to make an empty CompositeRestriction into an error, but you are correct that the code is currently allowing that.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, when we got an exception we can use the same test to verify it.

@njr-11 njr-11 merged commit 711497c into njr-11:829-dynamic-query-restrictions Nov 21, 2024
@otaviojava otaviojava deleted the 829-dynamic-query-restrictions branch November 21, 2024 20:20
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