Développement - Application mobile - React native

Bonjour, voici un résumé de la mission. L’idée est un test sur une feature. Si succés il doit y avoir un plus gros scope vous sera confié. Merci de signer le NDA si vous etes interessé.

Technologies choses:
Technologies chosen for the front-end will be the following:
• React-native
• React
• Relay
• Redux

Development Strategy:
The back-end is out of scope. While the back-end is being developed, the provider will work according to the following way:
• React-Native
• Redux
• Build Presentational components entirely
• The container components should return dummy data (They will be filled with Relay data afterwards)
• Use eslint-config-airbnb coding standard and enforce it as much as possible, every exception must be clearly explained
• Write tests with Enzyme and mocha (whatever assertion library you want, chai for example) (example here : [URL visible pour les membres Pro])
• DON'T have any state in the components, use the Redux store, it it's data you can pass dummy data from the container components to the presentational components
• use react-native-router-flux along with the Redux store
• The code should run on both Android and Ios
• Of course use ES6+ and React components as Classes
• Always define types and requirements for the components' props
• End-to-end tests are mandatory
Once the Api are available and the back-end is developed you will have to make the integration with relay
For team work and code review you will work in the following way:

Branching

In order to always have a working version of the code, no commits should be done on master. The general workflow we would like to have is
- Have one branch per feature
- When a feature is done, the developer creates a pull request
- The pull request is reviewed by peers and suggestions are made if there is something that should be changed
- Tests are run by continuous integrations servers to ensure that this new feature does no break any tests written before this feature
- When everything is fine the branch is merged

Committing

In order to make the git history clear and help code reviews, commits:
- Should be as as atomic as possible (ie. as often as possible), it is possible to commit even if a feature is not fully done, it does not matter since every work is done on a separate branch. 10 commits per day minimum.
- They should have a small title (It should respect the linux kernel convention to be less than 70-75 chars)
- They should have an extended description (wrapped at 72 characters per line)
- Generated code / code from external projects (ie. the code from react native starter kit), and Sportunity code, should not be in the same commit