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

Making FilterResponse not be a final record class #166

Merged
merged 1 commit into from
Dec 13, 2024

Conversation

jzonthemtn
Copy link
Member

Closes #165

@jzonthemtn jzonthemtn force-pushed the 166-filter-response-not-final branch from d979148 to d4e681a Compare December 2, 2024 01:55
@jzonthemtn jzonthemtn added this to the 2.10.0 milestone Dec 13, 2024
@jzonthemtn jzonthemtn merged commit ea9fdac into main Dec 13, 2024
22 checks passed
@jzonthemtn jzonthemtn deleted the 166-filter-response-not-final branch December 13, 2024 16:27
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.

FilterResponse should not be final so it can be extended in Philter and other applications
1 participant