README.md

Skygear x Redux Todos Example

LIVE DEMO

This example is extracted from the original Redux Example Project here.

This example shows how you can integrate Skygear JS SDK into the redux framework.

This project template was built with Create React App, which provides a simple way to start React projects with no build configuration needed.

Projects built with Create-React-App include support for ES6 syntax, as well as several unofficial / not-yet-final forms of Javascript syntax such as Class Properties and JSX. See the list of language features and polyfills supported by Create-React-App for more information.

Skygear Config

In this app, Skygear related APIs are wrapped inside src/api/skygear.js.

Example: You can import skygearAPI from src/api/skygear.js, and calling Skygear APIs with your code. (example in src/index.js)

import skygearAPI from './api/skygear'

skygearAPI.config(skygearContainer => {
  skygearAPI.signupAnonymously(user => { // Signup a skygear user 
    // Now we have a user to fetch the itmes from cloudDB
    store.dispatch(getAllTodos())
  })
});

Updating Skygear Endpoint and API Key

You should place you Skygear API Endpoint and API Key in src/api/skygear.js to connect this example to your Skygear app endpoint.

config: (cb) => {
    skygear.config({
      'endPoint': <API ENDPOINT>,
      'apiKey': <API KEY>,
    }).then(() => {
      console.log('skygear container is now ready for making API calls.');
      cb(skygear);
    }, (error) => {
      console.error(error);
    });
  }

Available Scripts

In the project directory, you can run:

npm start

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.

npm run build

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!

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.