Skip to content

WIP: [TEST-EXAM] Ready to check

Nicolas requested to merge jedi-test into master

Description

  • Change to webpack (no good reason .. not familiar with react-scripts, but it seems nice)
  • Add prettier/eslint configuration
  • Add local saving of new Jedi
  • Can kill a Jedi :'(
  • Add translation (FR/EN)
  • Add Sass
  • Using enzyme for UT on JSX component
  • Using jest for UT
  • Modular application
  • Using redux-observable to handle actions ( Rxjs more powerful than generator function in redux-saga)
  • ...

TODO

  • Lint file on push ?
  • More documentation
  • More Unit tests
  • E2E Tests (Cypress ? Nightwatch ?)
  • Use of PureComponent
  • Better use of Error boundaries
  • Use HOC
  • Use react-router with more new features
  • ...

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

Merge request reports