Skip to content

Allow settings.py postprocessor to be None #182

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
Merged
merged 4 commits into from
Aug 30, 2023
Merged

Allow settings.py postprocessor to be None #182

merged 4 commits into from
Aug 30, 2023

Conversation

Archmonger
Copy link
Contributor

By submitting this pull request you agree that all contributions to this project are made under the MIT license.

Description

  • The default postprocessor will be now disabled when REACTPY_DEFAULT_QUERY_POSTPROCESSOR is set to None.

Checklist:

Please update this checklist as you complete each item:

  • Tests have been included for all bug fixes or added functionality.
  • The changelog has been updated with any significant changes, if necessary.
  • GitHub Issues which may be closed by this PR have been linked.
@Archmonger Archmonger changed the title Allow settings.py postprocessor to be None Allow settings.py postprocessor to be None Aug 30, 2023
@Archmonger Archmonger marked this pull request as ready for review August 30, 2023 06:16
@Archmonger Archmonger requested a review from a team as a code owner August 30, 2023 06:16
@Archmonger Archmonger merged commit 82c80c3 into reactive-python:main Aug 30, 2023
@Archmonger Archmonger deleted the allow-none-postprocessor branch August 30, 2023 06:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
1 participant
@Archmonger