3291/listing export take 2

[ColinBuyck]

Pull Request Template

Issue Overview

This PR addresses #3291

• This change addresses the issue in full
• This change addresses only certain aspects of the issue
• This change is a dependency for another issue
• This change has a dependency from another issue

Description

This PR adds the listings export functionality along with associated tests! Column information here: https://docs.google.com/spreadsheets/d/1iMhybYs0RSdW940e402oI8xsqot8BlAYHaVTXaORIeA/edit#gid=670984196

How Can This Be Tested/Reviewed?

This can be tested by clicking the export to csv button on the partners side and verifying that the listing data is displayed correctly. Additionally, create your own listing to test cases that may not be present in our seed.

Checklist:

• My code follows the style guidelines of this project
• I have added QA notes to the issue with applicable URLs
• I have performed a self-review of my own code
• I have reviewed the changes in a desktop view
• I have reviewed the changes in a mobile view
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have assigned reviewers
• I have run yarn generate:client and/or created a migration if I made backend changes that require them
• My commit message(s) is/are polished, and any breaking changes are indicated in the message and are well-described
• Commits made across packages purposefully have the same commit message/version change, else are separated into different commits

Reviewer Notes:

Steps to review a PR:

• Read and understand the issue, and ensure the author has added QA notes
• Review the code itself from a style point of view
• Pull the changes down locally and test that the acceptance criteria is met
• Also review the acceptance criteria on the Netlify deploy preview (noting that these do not yet include any backend changes made in the PR)
• Either explicitly ask a clarifying question, request changes, or approve the PR if there are small remaining changes but the PR is otherwise good to go

On Merge:

If you have one commit and message, squash. If you need each message to be applied, rebase and merge.

[netlify]

✅ Deploy Preview for bloom-exygy-dev ready!

Name	Link
🔨 Latest commit	1b6dc8f
🔍 Latest deploy log	https://app.netlify.com/sites/bloom-exygy-dev/deploys/645bd6e1665a27000857b31e
😎 Deploy Preview	https://deploy-preview-3424--bloom-exygy-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[emilyjablonski]

Looking good! Just a few notes:

• In the status column I'm seeing "Public" or empty, could be intentional but might have assumed there would be different text in the draft state
• Are postmarks considered? isn't populating even if there is data

[ColinBuyck]

@emilyjablonski @ludtkemorgan Thank you both for the review! I've fixed the postmark issue and made the decision to shift "Are postmarks considered?" to just "Postmark" and show either the date or nothing. This mirrors the pattern used in Detroit. Do you have any concerns with this change @sarahlazarich?

As for the empty status, I realized I forgot to cover the closed state and that should be covered now! Good catch

For the jurisdictional admin piece, I made a bigger change to address that the story says "As a jurisdictional admin OR an admin in partners portal". The export should now function for both roles and will only show the permissioned listings for the respective user.

[ludtkemorgan]

🚈

[emilyjablonski]

🍭

[sarahlazarich]

no concerns with that change @ColinBuyck !