This guide will walk you through the steps required to migrate our Apollo 2.X implementation to the latest version. Most libraries have been consolidated into the top level export of @apollo/client but some are in separate sub folders. I primarily followed the official doc here
yarn add @apollo/clientyarn remove apollo-linkyarn remove apollo-link-httpyarn remove apollo-link-schema
| const cleanPatch = (patch, projectName, packageName, ignoredLines = []) => { | |
| // go through `ignoredLines` and remove them from `patch` | |
| let patchWithRenamedProjects = patch; | |
| patchWithRenamedProjects = patchWithRenamedProjects | |
| .replace( | |
| new RegExp('com\\.apolloschurchapp', 'g'), | |
| packageName | |
| ) | |
| .replace( | |
| new RegExp('com\\.apolloschurch\\.app', 'g'), |
Learn, build, test, repeat...
We need a team that is proficient in taking raw ideas from ministries and individuals and making them come to life. Currently there are too many places to take your idea. Does it go to technology and engineering? Does it go to the Innovation team? Does it need to go through the NPR process? These are all attempts to take an idea (or generate ideas internally) and craft a solution for a specific problem.
There is nothing wrong with these current methods but the biggest problem I see with any of them is the time it takes to go from idea to finished product. I believe a quick survey of staff would reveal a lack of confidence in our organizations ability to quickly deliver solutions to problems. What we need is a team designed from the ground up to take in ideas, build prototypes, and measure success. Rinse and repeat.
We were seeing two app icons in the drawer of our Android devices. Restarting the device, which solved this problem previously, did not help.
It was caused by adding a second launch activity into our Android manifest file. We did this when we upgraded Apollos versions. The new version uses RNBootsplashActivity as the launcher but we failed to remove the old launcher activity when upgrading. It also wasn't caught in testing.
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.newspringchurchapp">
I'm going to try and outline some things I think we should do to make the app more stable and possible steps to get there. Obviously all of this is up for discussion but also almost all of this will require conversations and outside of the engineering. It's urgent that we move forward so here's what I see.
We need to include integration testing into our app. We can use a platform called Detox. This will allow us to click buttons and simulate real time use.
Current Status: There is a PR in core to allow churches to pass props to the primitive components like buttons and views.
This will explain how to input sermon notes on a piece of content in Rock. It's a very simple process. They can be added and edited by anyone with Rock access and will show up in the app in 10 minutes or less.
First login to Rock, and click "Tools > Content".
I hereby claim:
To claim this, I am signing this object:
