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.
Issue
Description
Adds ability to filter by rent price based on data in the units summary table.
UI:

Type of change
How Can This Be Tested/Reviewed?
Performed some filtering a verified that the query was hitting the backend and the data was being filtered based on the units summary table.
NOTE: this is a little broken in certain cases, e.g. if you want to search for 2-bedrooms that are less than $600 a month, because the bedroom filter is looking at the units table, and the rent filter is looking at the summary table. We need way to generally determine which tables we should be joining to make queries. That's tracked in #530.
Checklist:
yarn generate:client
if I made backend changes