carlor / aao-react-native

The St. Olaf community, now in pocket size… rewritten in React Native.

AAO-React-Native

About

The St. Olaf community, now in pocket size… rewritten in React Native.

Download

• Android
• iOS

Getting Started

• Clone the repository
• cd into the folder
• Install React Native
• npm install
• npm run ios

Note

The Calendar might nag you for a Google Calendar API key. You can either ask someone involved with this project for a key, or you may create one yourself for use during development.

1. Create a copy of the .env.sample.js file and rename it to .env.js
2. Insert your API key in place of the key goes here text

Todo

• Bugs! All bugs should have the bug label in the issues
• Enhancements! All ideas for improvement that are not being worked on should be closed and labelled as discussion
• 3D touch actions for icon and within
• Touch-ID for SIS

Contributing

Would you like to contribute? Great! Have a look at React Native and make a pull request! PRs are required, so fork away and make one! If you feel like you should have write access to the repo, please make an issue and we can discuss it.

If you are looking to get a start with the project, issues tagged with all 3 good first change, discussion, and closed are a great place to start. These issues are ones that the team has identified as simple, small changes that won't get too deep, and will be easy to approve for merging. See our todo section if you are curious why they are tagged as closed. They really are open!

We use two continuous-integration (CI) systems to make sure that the project still works as we change things. Any submissions you make will be validated by Travis and AppVeyor, the CIs.

As always, please keep the Code of Conduct in mind.

Before you commit and push, make sure to lint your changes and fix any errors or warnings that npm run lint shows. We try to keep the master branch clean of all messages from eslint. ) are a great place to start. These issues are ones that the team has identified as simple, small changes that won't get too deep, and will be easy to approve for merging. See our todo section if you are curious why they are tagged as closed. They really are open!

We use two continuous-integration (CI) systems to make sure that the project still works as we change things. Any submissions you make will be validated by Travis and AppVeyor, the CIs.

As always, please keep the Code of Conduct in mind.

Before you commit and push, make sure to lint your changes and fix any errors or warnings that npm run lint shows. We try to keep the master branch clean of all messages from eslint.