Redadalertas

A tool that will provide real-time, verified alerts to people about immigration raids.

Check out the Wiki

This repo will serve as the front end, in the form of a web application. It can be considered a proof-of-concept for a mobile app. We will be using React.js and the React Toolbox Library.

If you are interested in helping build out the API, go to https://github.com/Cosecha/redadalertas-api.

How to join the project

To learn how to be part of the project, check out the wiki.

Contributor Covenant

The maintainer of this project is committed to making sure this project provides a safe space for people of all genders, races, and levels of programmer proficiency. Everyone has something valuable to contribute.

We will also enforce our Contributor Covenant Code of Conduct should you engage in behaviors not in line with the project's, and Movimiento Cosecha's values.

Not a Developer, How Can I Contribute?

There are plenty of ways:

• Read the wiki to learn more about how the project is organized.
• Join the gitter chat room.
• Share this repo with your developer friends that might want to contribute.

This project was bootstrapped with Create React App.

Below you will find some information on how to perform common tasks.<br> You can find the most recent version of this guide here.

Table of Contents

• Updating to New Releases
• Sending Feedback
• Folder Structure
• Available Scripts
  • npm start
  • npm test
  • npm run build
  • npm run eject
• Syntax Highlighting in the Editor
• Displaying Lint Output in the Editor
• Changing the Page <title>
• Installing a Dependency
• Importing a Component
• Adding a Stylesheet
• Post-Processing CSS
• Adding Images and Fonts
• Using the public Folder
  • Changing the HTML
  • Adding Assets Outside of the Module System
  • When to Use the public Folder
• Using Global Variables
• Adding Bootstrap
• Adding Flow
• Adding Custom Environment Variables
• Can I Use Decorators?
• Integrating with an API Backend
  • Node
  • Ruby on Rails
• Proxying API Requests in Development
• Using HTTPS in Development
• Generating Dynamic <meta> Tags on the Server
• Running Tests
  • Filename Conventions
  • Command Line Interface
  • Version Control Integration
  • Writing Tests
  • Testing Components
  • Using Third Party Assertion Libraries
  • Initializing Test Environment
  • Focusing and Excluding Tests
  • Coverage Reporting
  • Continuous Integration
  • Disabling jsdom
  • Snapshot Testing
  • Editor Integration
• Developing Components in Isolation
• Making a Progressive Web App
• Deployment
  • Serving Apps with Client-Side Routing
  • Building for Relative Paths
  • Firebase
  • GitHub Pages
  • Heroku
  • Modulus
  • Netlify
  • Now
  • S3 and CloudFront
  • Surge
• Advanced Configuration
• Troubleshooting
  • npm start doesn’t detect changes
  • npm test hangs on macOS Sierra
  • npm run build silently fails
  • npm run build fails on Heroku
• Something Missing?

Updating to New Releases

Create React App is divided into two packages:

• create-react-app is a global command-line utility that you use to create new projects.
• react-scripts is a development dependency in the generated projects (including this one).

You almost never need to update create-react-app itself: it delegates all the setup to react-scripts.

When you run create-react-app, it always creates the project with the latest version of react-scripts so you’ll get all the new features and improvements in newly created apps automatically.

To update an existing project to a new version of react-scripts, open the changelog, find the version you’re currently on (check package.json in this folder if you’re not sure), and apply the migration instructions for the newer versions.

In most cases bumping the react-scripts version in package.json and running npm install in this folder should be enough, but it’s good to consult the changelog for potential breaking changes.

We commit to keeping the breaking changes minimal so you can upgrade react-scripts painlessly.

Sending Feedback

We are always open to your feedback.

Folder Structure

After creation, your project should look like this:

my-app/
  README.md
  node_modules/
  package.json
  public/
    index.html
    favicon.ico
  src/
    App.css
    App.js
    App.test.js
    index.css
    index.js
    logo.svg

For the project to build, these files must exist with exact filenames:

• public/index.html is the page template;
• src/index.js is the JavaScript entry point.

You can delete or rename the other files.

You may create subdirectories inside src. For faster rebuilds, only files inside src are processed by Webpack.<br> You need to put any JS and CSS files inside src, or Webpack won’t see them.

Only files inside public can be used from public/index.html.<br> Read instructions below for using assets from JavaScript and HTML.

You can, however, create more top-level directories.<br> They will not be included in the production build so you can use them for things like documentation.

Available Scripts

In the project directory, you can run:

npm start

Runs the app in the development mode.<br> Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.<br> You will also see any lint errors in the console.

npm test

Launches the test runner in the interactive watch mode.<br> See the section about running tests for more information.

npm run build

Builds the app for production to the build folder.<br> It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.<br> Your app is ready to be deployed!

See the section about deployment for more information.

npm run eject

Note: this is a one-way operation. Once you eject, you can’t go back!

If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

Syntax Highlighting in the Editor

To configure the syntax highlighting in your favorite text editor, head to the relevant Babel documentation page and follow the instructions. Some of the most popular editors are covered.

Displaying Lint Output in the Editor

Note: this feature is available with react-scripts@0.2.0 and higher.

Some editors, including Sublime Text, Atom, and Visual Studio Code, provide plugins for ESLint.

They are not required for linting. You should see the linter output right in your terminal as well as the browser console. However, if you prefer the lint results