fix: DAH-3176 hide directory 1.5 change

[tallulahkay]

Description

Makes sure sections are hidden unless there are listings, until directory 1.5.

Jira ticket

https://sfgovdt.jira.com/browse/DAH-3176

Checklist before requesting review

Version Control

• branch name begins with angular if it contains updates to Angular code
• branch name contains the Jira ticket number
• PR name follows type: TICKET-NUMBER Description format, e.g. feat: DAH-123 New Feature. If the PR is urgent and does not need a ticket then use the format urgent: Description

Code quality

• the set of changes is small
• all automated code checks pass (linting, tests, coverage, etc.)
• code irrelevant to the ticket is not modified e.g. changing indentation due to automated formatting
• if the code changes the UI, it matches the UI design exactly
• if the changes include human translations, follow the human translations process

Review instructions

• instructions specify which environment(s) it applies to
• instructions work for PA testers
• instructions have already been performed at least once

Request review

• PR has needs review label
• Use Housing Eng group to automatically assign reviewers, and/or assign specific engineers
• If time sensitive, notify engineers in Slack

[jimlin-sfgov]

LGTM

@tallulahkay Were you planning to do a hotfix? If so, did you mean for the target branch to be main?

Edit: or merge to main, then cherrypick to release branch, then re-deploy? I forget if we settled on a new hotfix procedure. CC @alulabeshue-sfgov

[alulabeshue-sfgov]

LGTM

@tallulahkay Were you planning to do a hotfix? If so, did you mean for the target branch to be main?

Edit: or merge to main, then cherrypick to release branch, then re-deploy? I forget if we settled on a new hotfix procedure. CC @alulabeshue-sfgov

We landed on treating a hotfix like any other feature change. I think we can merge this back into main and start a new release, even though it is a single change.