easy_apply

[thebigG]

Hello everyone!

These are some of the changes I made:

• "easy_apply" is now a sub-command of JobFunnel.
• easy_apply will look at the master_lis csv file that is passed to JobFunnel and open(by default 1) tab on the user's web browser random job and mark the row that matches that link in the csv with the status "archive"(by default).
• easy_apply warns the user at 30 or more tabs before opening all of the tabs together on their web browser.
• All the options for easy_apply are prefixed with "ea".
• "--ea_number x" specifies that x number of tabs will opened in the browser and that x number of rows containing those links will be marked with the status the user passed.
• "--ea_output x" specifies that x will be the output file for easy_apply. This output file is used in conjunction with the master_list file. Both the the output_file for easy_apply and master_list will have the same exact data on them after running easy_apply.
• "-ea_status x" says that the rows that are opened on the browser will be marked with status "x". The only valid statuses for now are:["archive", "interview", "offer"].
• As of right now if "easy_apply" is passed to JobFunnel, there is no web scraping done. The main module simply returns if the "easy_apply" option was passed.

Hope this is clear enough :)

[studentbrad]

I believe that maybe I should play devil's advocate here. This seems beyond the scope of this project and may be the perfect opportunity to exercise the usefulness of forks in GitHub. Forks can have features that the repository does not have. Hence, the author can add features that they think are useful. Adding this as a feature to the project could ultimately discourage users. Given how complex the project has already become I am afraid that going down this road could put it in a grave. I will leave the decision to @PaulMcInnis as he is the owner of this repository.

[itSeez]

Recall the Unix philosophy. Tools should have one job and do it well.

[PaulMcInnis]

RE: behaviour with archive - it removes them and adds them to be filtered away next time data comes in.

I see lots of value in this tool - but I’m gonna side with the community on this one since it goes a fair bit beyond the original intent.

Please don't be discouraged from contributing in the future however :)

We’re updating some of the guidance around contributing to help direct future work as well - sorry about the ambiguity around this.