sirandrii/chromeextensionineed

Chrome estension for skipping unrelevant indeed job descriptions

chromeextensionineed's Issues

Optimize calling functions in mutation.observer

When a document is mounted we should firstly remove jobs by title only then highlight words in the description

Update readme

New functionality was added. Update available features, demoGif, and installation steps

make new screenshots

Add new screenshots to chrome extension store

added years highlighter

Users should have the ability to define triggers of highlighting years range of experience.
If user chooses 5 years, then everything that is equal or more must be highlighted by patterns 5 years|5+ years

new feature: remove visited

Add function for removing visited job-descriptions
Add a checkbox to store this in the app, it's not necessary to be in the initital state.

Critical bug: random work of highlighter

Sometimes highlighter is not working.

Something has changed on indeed recently, after the extension highlighted words, the DOM tree updated again and inject a new HTML element. I think that it copy DOM tree and then after async action replaces the updated by me one.

Do auto-refresh after Save button click

Extension manipulates the real DOM and requires a page refresh to apply changes after the user clicks the Save button. I'd like to add an auto-refresh feature to improve user experience.

Suggestions:

• Look for chome API that can reload Tab after saving
• Provide visual feedback (e.g. toast notification) to inform the user that the page is refreshing.

Add input with years of experience to interface

Update interface:

• Add input to highlight years of experience
• add a checkbox to turn on/off highlight by years

Build a CI/CD pipeline for a Chrome extension using GitHub

register extension in the Crome webStore
create Pipeline for updating extension in webStore, after master branch were changed

refactor higlighters - make them modular

Put highlighters in separate files to make code more cleaner

update icons

Create unique icons for extension

Implement Singleton Pattern

Currently, the extension has three entry points (options, content, service-worker). Singelton may be a good fit for making content.js more modular and not passing initialized storage as a parameter to split functions or access chrome's storage by API

Bug: LI with remove word unpredictable behaviour

After implementing PR #4, sometimes item lists has the wrong class and became unclickable