Support CSV output

[elimelt]

Add support for CSV output. See email_scraper/formatters/json.py as an example.

Note:

We can either validate that the data is un-nested and error if not, or just turn all values into strings. I prefer the validation approach, but would potentially get behind the addition of a --unchecked flag or something like that to override checks and manually convert to string

[radon1743]

Hi, elimelt

I'll be working on this issue, as mentioned we'll check data for un-nested and throw error if not, with a additional --uc or --unchecked flag to override the checks to convert the nested data to String.

I am doing this for the first time, guidance would be appreciated.

[elimelt]

Hi, @radon1743! Great job being all proactive B)

We'll be reaching out with next steps but they aren't needed for you to get to work coding. I'll assign you to the issue now, so feel free to start getting comfortable with the code base in the meantime!

In terms of guidance, definitely come to tomorrow's meeting if you're able to make it. We'll talk about resources then. Otherwise I'm always available via Discord @elimelt

[elimelt]

Ah, I just realized you're an outside contributor. No issue with me, although you should know this is part of a program run by the Software Engineering Career Club at the University of Washington. If you're looking for guidance, you should consider signing up and joining our club:

https://labs.swecc.org
https://swecc.org

Since you won't be at tomorrow's info session, I'll need a few things from you before assigning the issue to you (I'm moving it out of unclaimed so it is no longer up for grabs however).

1. When are you planning on working on this? Any idea when you'll start?
2. How long do you want me to wait before checking back in? The actual code changes shouldn't be very complicated at all.

Once you reply with this info I'll reassign the issue to you. This just helps me with book keeping

[radon1743]

I don't think I'll be able to attend most of the sessions due to different time zones.

1. I have forked this repo and started working on this already.
2. By the end of this month I'll post a pull request.

I had some ideas regarding the project like:

• Using a shared state for file formats in the cli.py will be optimal

Since I am an outsider contributor idk if I'm allowed to change basic structure of things, so I was hesitant to go forward.

I'll fill out form for joining the club though you should know, I am not a student of University of Washington or for that matter I am not even a citizen of USA.

Thanks for cooperation.

[elimelt]

I don't think I'll be able to attend most of the sessions due to different time zones.

1. I have forked this repo and started working on this already.
2. By the end of this month I'll post a pull request.

I had some ideas regarding the project like:

• Using a shared state for file formats in the cli.py will be optimal

Since I am an outsider contributor idk if I'm allowed to change basic structure of things, so I was hesitant to go forward.

I'll fill out form for joining the club though you should know, I am not a student of University of Washington or for that matter I am not even a citizen of USA.

Thanks for cooperation.

(1) Awesome!
(2) Sounds good, I'll check back in with you March 1!

I'm not 100% sure what you mean by a shared state, could you clarify a little?

You are certainly allowed to reorganize stuff and refactor to your heart's content, but please do try to keep PRs a reasonable size. If you'd like to do a larger refactor outside of enabling CSV output, feel free to create an issue and submit another PR.

Luckily this project has no dependency on you being a UW student!

Also don't forget to submit a PR adding yourself as a contributor to https://github.com/swecc-uw/swecc-labs