Skip to content

rohitspujari/demo-app

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

56 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

This project was bootstrapped with Create React App and AWS Amplify.

Add New Project

  • Edit projects.json file in top level Projects folder. Add name [MyProject], navigation [/myproject], and description.
  • Create a new folder [MyProject] under Projects.
  • Create index.js file, create a react component named [MyProject] (using rcc)
  • Edit App.js file, import [MyPreoject] component created in above step.
  • Register new route with [/myproject] path

Resources

AppSync Lambda Client Lambda Layer Blog - Dependencies

How to programmtically Switch Routes

Challenges with lambda

Using Promises with AWS APIs

Notes

Amplify CLI doesn't automatically configure AWS_IAM authentication mode for graphql. The defualt auth mode is cognito user pool.C ongnito user pool restricts the graphql endpoint access through web apps only. To enable accessing graphql endpoint from other services like lambda, we need to customize the authentication, and set the authRole on cognito identity pool the auth role should have permission to invoke required graphql api http://sandny.com/2018/09/24/appsync-graphql-amplify-iam/

Amplify React Native auth.signout() does not return to Sign In page aws-amplify/amplify-js#1529

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 test

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

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!

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.

Learn More

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.

About

amplify app

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published