Skip to content

Latest commit

 

History

History
136 lines (92 loc) · 6.87 KB

README.md

File metadata and controls

136 lines (92 loc) · 6.87 KB
Raw

What is this?

This is the code for the RECAP Chrome, Firefox, and Safari extensions, programs that are used to liberate millions of documents from the PACER system. To install this extension please visit its homepage at https://free.law/recap/.

Reporting Issues

Issues go one of a few places:

Joining as a Developer

If you wish to contribute to our efforts to drain PACER, please get in touch using the contact form on Free Law Project's website or simply get to work on an issue that interests you. It's usually better to get in touch before you begin work though.

Code Standards

  1. We have an eslint configuration (.eslintrc.js). Please try to ensure that new commits conform to it, but many existing files unfortunately do not. There are probably plugins for your editor to help you with this.

  2. For commits, please adhere to the guidance published here. Intellij has a plugin to help with this. Look for "Git Commit Template".

Tips for Making Extensions

  1. The weirdest thing about working on extensions is that you need to have two developer tool windows open simultaneously. One for the page you're on and how the extension interacts with it, and the other for the background page of the extension. You'll just have to live like this. Having multiple monitors helps. Read on for how to set this up.

  2. You can load an "unpacked extension" from chrome://extensions/ if you enable developer options in Chrome. The same can be accomplished in Firefox by going to about:debugging, clicking "Load Temporary Add-on" and then selecting any file.

    Once you have the unpacked extension loaded, you'll see a button to debug it. Click that to open the second developer tools window mentioned just above.

  3. While it's true that every court has their own customized version of PACER, there is a PACER training site that does not charge fees. You can use this if you wish to work on the system without accruing charges. If you are accruing charges while working on this extension, Free Law Project may be able to help. Let us know.

  4. If you want to auto-zip your code on changes, you have two options. First, you can install a utility called entr and run:

     command ls *.js | entr zip -FSr recap-chrome.zip * --exclude=*node_modules*

    Alternatively, for Firefox, you can use the web-ext tool, with a command like:

     web-ext run --firefox-profile recap-debugging --start-url https://ecf.dcd.uscourts.gov/cgi-bin/DktRpt.pl?178502 --start-url https://www.courtlistener.com/docket/4214664/national-veterans-legal-services-program-v-united-states/

    To run that you'll need a recap-debugging profile first, but running that will set up auto-reload of the extension in Firefox. It will also load a couple useful URLs in your debugging window.

Running Tests

You can (and should) run the tests before you push. If you don't, you'll be disappointed when our continuous integration suite yells at you. To run tests, install the dependencies described in package.json by running:

npm install

You will need Chrome installed. Then run:

karma start --single-run

If the tests pass, give a push to your repo and send us a pull request.

When we pull your code using Github, these tests will be automatically run by GitHub Actions. You can make sure that your pull request is good to go by waiting for the automated tests to complete.

For more information on testing see TESTING.md.

The current status of our master branch is:

Build Status

Releasing a New Version

When a new version is needed, the release process is:

  1. Do the manual QA tests

  2. Update package.json and manifest.json with a new release version.

  3. Update CHANGES.md

  4. Commit the code.

  5. Tag the code with something like:

     git tag -s '0.8.4' -m "Releases 0.8.4, fixing replaceState and pushState to work in Chrome 43." -u '[email protected]' -f
 git push --tags -f

  6. Make sure you don't have any working/testing code in your tree that could get zipped up in the next step.

  7. Run the following commands in your terminal from the project root directory to create release packages for Chrome and Firefox in the build folder:

     npm run release-chrome
 npm run release-firefox

    The build.sh script relies on the jq command-line JSON processor. Make sure you have it installed before proceeding.

  8. Make a new release on Github announcing the release that includes the .zip files in the release assets.

  9. Upload the chrome-release.zip file to the Chrome Web Store..

  10. Upload the firefox-release.zip file to addons.mozilla.org.

Copyright

RECAP for Chrome Copyright 2013 Ka-Ping Yee [email protected]

RECAP for Chrome is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. RECAP for Chrome is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with RECAP for Chrome. If not, see: http://www.gnu.org/licenses/