Fixing chrome extension: making it dynamic

[AliyahHA]

Problem

Other users unable to use Chrome merger extension because developers hard-coded it.

Why is this important?

Solution

Aiming to make chrome extension work by changing reference to StARS in RIPS URL link.

Implementation Steps

Two main steps: 1) Working in making RIPS merger chrome extension work locally.

2) Working in making RIPS merger chrome extension work through google extension store so it is easily accessible for everyone.

[Beamanator]

Perfect @AliyahHA 👍 One note: We want to make the chrome extension work... For a certain organization (I always forget which) so if I were you I would mention that in your steps to be super specific 👍

[Beamanator]

Useful link to learn about content scripts, in the chrome extension manifest.json file: https://developer.chrome.com/docs/extensions/mv3/content_scripts/

[Beamanator]

Challenge for @AliyahHA : Get the extension running locally and make sure all of the steps work and are clear

1. Follow these steps:
   • https://github.com/Beamanator/RIPS-Duplicate-Merger-CExt#getting-started
   • https://github.com/Beamanator/RIPS-Duplicate-Merger-CExt#updating-extension-locally
2. Write down all of the difficult things you ran into. Try to solve them using google or friends.
3. If there is anything you haven't figured out, we will solve them together
4. At the end, we'll update the instructions to be as clear as possible

[AliyahHA]

Hi @Beamanator I got the extension running locally following the steps on Getting Started section:( https://github.com/Beamanator/RIPS-Duplicate-Merger-CExt )

2. Difficulties faced: in the Getting Started notes section it did not specify that I need to actually clone the repo and create a folder in my desktop. This got me thinking a bit and I had to check and figure it out.

[Beamanator]

Nice @AliyahHA ! Good point about that, let's update the documentation to explain those steps! Can you try to come up with clear steps, then we can add that to the documentation?

[Beamanator]

So here's some things I think we can add to the README to make it better:

1. A "table of contents" section with links to sections below (like this: https://github.com/expensify/App#table-of-contents)
2. In the Getting Started section, add some instruction about cloning the repo onto your computer, something like this:

1. Download the code from this repository on your computer by clicking the "Code" -> "Download ZIP" buttons at the top of the page
2. Extract the folder from the ZIP file
   • On Windows, right click on the ZIP file, then click "Extract"
   • On MacOS, just double-click the file
     3. In your terminal, change directory to the file you just downloaded
     4. Run npm install to install the node packages in the package.json file
     5. ... (continue existing steps)