mattcheah / cover-letter-snippets Goto Github PK

After parsing a job description, in ResultsComponent, the only categories that are displayed are the ones that have matches in the job description. However, this isn't always practical. For example, if a job is looking for javascript developers who have experience in javascript frameworks, a category for Angular or React isn't going to show up. Users need to have the ability to scroll through additional categories even if there are no matches in the job description text.

This change can be made in ResultsComponent. The results are currently being displayed and filtered by a pipe hasKeywords. You could change the pipe so you can pass values to it (eg. showAllValues: showAllValues and on the Show More Button: (click)="showAllValues = !showAllValues")
Or you can do it however else you want.

This is a fairly quick fix for newcomers, and I would love to help in any way possible so just let me know if anyone wants to take this on and needs help. Thanks!

It would be much easier to compose a cover letter if the user is able to see the job description to understand what the employer wants to focus on. We need to find a way to display the parsed job description so that the user can see it when he/she needs to.

Ideas for how to accomplish this:

• Create a popover that shows the job description once you hover your mouse over a link.
• Add an accordion style slide-down/slide-up toggle so that the user can see the job description when they need to, but so that it doesn't take up valuable real-estate when actually adding snippets to their cover letter.
• (Desktop only) move the app to the left or right, so and flex or float the job description onto the other side.

If anyone wants to take this on I'm more than happy to answer questions or guide someone through this. Thanks!

Specifically for solving issues, I'm not able to get the gist of what this site is or how to get it up and running locally so that I can either make changes or contribute to it. Updating the readme as per a getting started up and running methodology would help greatly.

Currently, if a job description lists PHP7 and a user's category is php, the description parser will not pick this up as a keyword. Same for similar things like ruby/rails vs rails, or ecmascript6 vs es6.

In order to make the parser more efficient at finding the most relevant keywords/categories, we need to have an option to edit categories to have an array of aliases that will also trigger a snippet's categories when the application parses the job description.

What this will most likely involve:

• Creating a new database table of categories names, and an array of aliases.
• Creating a new component and CRUD routes in DatabaseService for editing the category database.
• Rearranging the view a little bit to include forms to make category editing happen.
• Updating ParseDescriptionService to check each word against a category's alias array.

If you'd like to help out, leave a comment and I'd be more than happy to walk you through or share some opinions. Thanks!

I tried to use the Connect to JSON file functionality, but on clicking the button, nothing happens. I think this is a recent bug, because I remember being able to use the functionality when I first tried the app back in October.

Addable snippets with the most amount of categories that match job description keywords should be the first ones to show up in the list. eg. If a job description asks for Java, C, Python, and R, my saved cover letter snippet that mentions Java, C, and Python should show up above my snippet that just mentioned Java, or even one that mentions Java and R.

Let me know if you'd like to help out and I'll provide any information I can!

It's kind of a pain to have to create an mlab database instead of just creating a JSON file locally.
We need to implement an option for creating/using a local JSON file. This would affect the following files/components:

• index.js (main entrypoint. We'd need to set up different routes for making changes to the file.)
• DatabaseComponent - The view needs to be updated with a button that creates or searches for an existing JSON file. The component itself needs to be updated with logic that calls the Database Service and sets an appropriate option so that the rest of the app knows to use JSON.
• DatabaseService - call the appropriate endpoints when making requests.
• Probably a few other components and services.

This is a little more difficult because it will affect the entire app. If anyone needs any advice on how to go about doing this, I'd be happy to help. Thanks!

Currently, no snippets in the database are shown after parsing the job description, and the user must click on "Show Snippets" for a specific category to show any cover letter snippets in the database.

Since most users would always start off with an introduction, the first category of snippets to show from the database should be the "intro" snippets. It should show immediately after parsing the job description, not just after the "Show Snippets" button is clicked.

The logic for this is located in the ResultsComponent and retrieves records form the DatabaseService.database object.
A callback can be initiated after the ParseDescriptionService is finished, which runs the function displaySnippets('intro') in ResultsComponent, or it can be done some other way.

I'd be happy to help out with anyone who wants to take this on.