Code review 12.12.2018 #27
Labels
🐞 bug
Something isn't working
📈 enhancement
New feature or request
good first issue
Good for newcomers
Overall view on the project is positive, code is nicely structured, no big files or mess in codebase. Bonus points are for using React hooks, Typescript. Apollo and Ramda - it’s good fit for this kind of internal project.
Issues
There is not much to point out, but still there is one issue that must be fixed.
git clone
>nom install
>nom start
. For frontend projects.env
file(s) should be committed as values in those are not actual secrets. See Dan Abramovs comment for more info: https://github.com/facebook/create-react-app/issues/2403#issuecomment-304624540Enhancements
Here is few minor issues that would be nice to get rid of:
package.json
,tslint.json
andtsconfig.json
are several packages/rules that are unnecessary or shouldn’t be used.packages.json
tslint.json
tsconfig.json
process.env.REACT_APP_…
shouldn’t be used directly. Rather import them from sharedconfig.js
file.../../..
. Addbabel-plugin-module-resolver
andpaths
in tsconfig. Here is example config:.babelrc
tsconfig.json
.babelrc
:babel-plugin-ramda
enables imports likeimport { map } from 'ramda’
- no need to writeramda/es/map
:)babel-plugin-styled-components
will provide display name for better debugging.stylelint
lint-staged & tsc
in case there is error.Summary
👍 Using React hooks
👍 Very clean codebase
〰️ Bloated package.json. tsconfigand tslint
〰️ env values used directly
👎 Project needs additional configuration which is not provided - missing .env
The text was updated successfully, but these errors were encountered: