An application to find the nearest free workspaces for the remote workers in all of us. We are a team of developers and UX designers who met while attending our respective bootcamps at General Assembly. We are currently working towards our very first MVP.
In order to run on localhost, you need a valid google maps api key. You must create a .env.local
file inside ./src to save your key in the following format:
REACT_APP_GOOGLE_API_KEY={enter_valid_api_key}
Install dependencies with
npm install
Run the development server with
npm start
This project was bootstrapped with Create React App.
<Map />
also see: onDblclick, onRightclick
onClick={this.handleClick}
// handleClick is a method
handleClick = (props, map, event) => {
// gives you access to all map props
// gives you access to the map object
// event object
}
also see onDragstart
onDragend={this.handleDrag}
handleDrag = (props, map) => {
// gives you access to all map props
// gives you access to the map object
}
onZoom_changed={this.handleZoom}
handleZoom = (props, map) => {
// gives you access to all map props
// gives you access to the map object
}
onCenter_changed={this.handleCenter_change}
handleClick = (props, map) => {
// gives you access to all map props
// gives you access to the map object
}
onBound_changed={this.handleBounds_change}
handleBounds_change = (props, map) => {
// gives you access to all map props
// gives you access to the map object
}
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.