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.

Sign up for GitHub

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

Jump to bottom

FilterResponse should not be final so it can be extended in Philter and other applications #165

Closed
jzonthemtn opened this issue Nov 25, 2024 · 0 comments · Fixed by #166
Closed

FilterResponse should not be final so it can be extended in Philter and other applications #165

jzonthemtn opened this issue Nov 25, 2024 · 0 comments · Fixed by #166
Assignees
@jzonthemtn
Milestone
2.10.0

Comments

@jzonthemtn
Copy link
Member

FilterResponse should not be final so it can be extended in Philter and other applications. In Philter, there is a use-case for adding to the response but FilterResponse is a record class (and final).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jzonthemtn jzonthemtn

Labels
None yet
Projects
None yet
Milestone
2.10.0
Development

Successfully merging a pull request may close this issue.

Making FilterResponse not be a final record class philterd/phileas
1 participant
@jzonthemtn