##METEOR LOCATOR APP This app was created as part of the Tier 3 Solo challenge prework for chingu.
Notes: I am not a react developer but choose this a sI wanted a nice lighter front end then Rails and wanted to use state.
The initial call to the API only selected the first 1000 records. Initally I hard coded the 45716 in to the APi call. Until someone mentioned you could use count in a query. So now I am doing two API calls one to get the count of records, and a second to then get all records.
They may be a better way of doing this, but once I have them all in state I wanted to manipulate the data on the client. Rather then making multiple API calls.
I was going to do my own pagination on a Meteor objects, until I discovered ANT tables which does most of the heavy lifting.
I have set a 5 second time limit on both the api calls for if the API is slow, though this should never hit. There is a "Loading" state and an "Error" state which is triggered by the catch statements.
I originally wanted to use Mapbox react but couldnt get it to render correctly. SO I have fallen back to using p5.js which I have used to plot Eathquake data on before, however this is the first time using the react wrapper around it. I have limited the rending to 100 meteors on the map to keep the app snappy.
I have added a few helpers to format data and numbers.
Search is more fuzzy search then a direct comparison starting from the beginning of the string. Also if nothing is matched then I will return all meteors.
This project was bootstrapped with Create React App.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build folder.
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.
Your app is ready to be deployed!
See the section about deployment for more information.
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.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify