DO NOT MODIFY OR CHANGE THE CODE BEFORE CONFIRMED BY DOOBOOLAB
. THIS REPOSITORY IS USED IN DOOBOO-CLI
.
Specification
- react
- react-router
- typescript
- styled-components
- ts-jest
- react-testing-library
- react-hook
- prettier
- self localization
- Sample of context-api with
react-hook
(useContext
). - Know how to structure react web app with
typescript
. - Know how to navigate between screens with
react-router
. - Know how to write test code with
react-native-testing-library
. - Know how to
lint
your project witheslint
. - Know how to localize your project.
- Know how to place your
retina image
into your project. - Know how to use
styled-component
. - Know how to implement theming with styled-component.
app/
├─ assets
│ └─ icons // app icons
│ └─ images // app images like background images
├─ docs // explanation for dev stack we used. (Sorry for Korean)
├─ node_modules/
├─ src/
│ └─ apis
│ └─ components
│ └─ contexts
│ └─ providers
│ └─ types
│ └─ utils
│ └─ App.tsx
│ └─ theme.ts
├─ test/
├─ .eslintrc.js
├─ .gitignore
├─ babel.config.js
├─ environment.d.ts
├─ jest.config.js
├─ package.json
├─ postcss.config.js
├─ README.md
├─ STRINGS.js
├─ tsconfig.json
├─ typings.d.ts
├─ webpack.config.js
└─ webpack.config.prod.js
Installing and running the project is as simple as running
yarn && yarn start
- Note that we recommend using yarn.
This runs the start
script specified in our package.json
, and will spawn off a server which reloads the page as we save our files.
Typically the server runs at http://localhost:8080
, but should be automatically opened for you.
Testing is also just a command away:
yarn test
PASS src/components/shared/__tests__/Button.test.tsx
PASS src/components/screen/__tests__/Intro.test.tsx
Test Suites: 2 passed, 2 total
Tests: 4 passed, 4 total
Snapshots: 2 passed, 2 total
Time: 2.145s, estimated 3s
We've created test examples with jest-ts in src/components/screen/__tests__
and src/components/shared/__tests__
. Since react is component oriented, we've designed to focus on writing test in same level of directory with component. You can simply run yarn test
to test if it succeeds and look more closer opening the source.
These are preferred settings for auto linting and validation
- with prettier extension installed
- with eslint extension installed
"eslint.enable": true,
"eslint.validate": [
"javascript",
"javascriptreact",
"typescript",
"typescriptreact"
],
// prettier extension setting
"editor.formatOnSave": true,
"[javascript]": {
"editor.defaultFormatter": "esbenp.prettier-vscode"
},
"[javascriptreact]": {
"editor.defaultFormatter": "esbenp.prettier-vscode"
},
"[typescript]": {
"editor.defaultFormatter": "esbenp.prettier-vscode"
},
"[typescriptreact]": {
"editor.defaultFormatter": "esbenp.prettier-vscode"
},
"prettier.singleQuote": true,
"prettier.trailingComma": "all",
"prettier.arrowParens": "always",
"prettier.jsxSingleQuote": true
Whenever you add your own Context provider you can add it to providers/
and use it inside of providers/index.tsx
// Add providers here
const RootProvider = ({
initialThemeType,
children,
}: Props): React.ReactElement => {
return (
<AppProvider>
<ThemeProvider
initialThemeType={
initialThemeType === ThemeType.LIGHT ? ThemeType.LIGHT : undefined
}
>
{children}
</ThemeProvider>
</AppProvider>
);
};
The RootProvider
is being used at App.tsx
and test files easily
// App.tsx
function App(): React.ReactElement {
return (
<RootProvider>
<SwitchNavigator />
</RootProvider>
);
}
// test files
const component = (props): React.ReactElement => {
return (
<RootProvider initialThemeType={ThemeType.LIGHT}>
<Intro {...props} />
</RootProvider>
);
};
using consistent theme(ThemeType.LIGHT as default) explicitly is encouraged in testing for avoiding unexpected snapshot test errors
We've defined localized strings in assets/lang/en.json and ko.json
.
// en.json
{
"BUTTON": "Button",
"SIGNUP": "Sign Up",
"LOGIN": "Login",
"LOGOUT": "Logout",
"GOOGLE_LOGIN": "Login with Google",
"FACEBOOK_LOGIN": "Login with Facebook",
"EMAIL": "Email",
"EMAIL_HINT": "Write email address.",
"PASSWORD": "Password",
"PASSWORD_HINT": "Write password.",
"COMPLETE": "Done",
"GOTO_Temp": "No Page",
"BACK": "Back",
"NAVIGATE": "Navigate",
"CHANGE_THEME": "Change theme"
}
// ko.json
{
"BUTTON": "버튼",
"SIGNUP": "회원가입",
"LOGIN": "로그인",
"LOGOUT": "로그아웃",
"GOOGLE_LOGIN": "구글 로그인",
"FACEBOOK_LOGIN": "페이스북 로그인",
"EMAIL": "이메일",
"EMAIL_HINT": "이메일 주소를 입력해주세요.",
"PASSWORD": "비밀번호",
"PASSWORD_HINT": "비밀번호를 입력해주세요.",
"COMPLETE": "완료",
"GOTO_Temp": "없는 페이지",
"BACK": "뒤로",
"NAVIGATE": "이동하기",
"CHANGE_THEME": "테마 변경"
}
-
How it is used
Import locales in
assets/langs
. Currently,ko.json
anden.json
is installed. If you want to add more languages you can add it inSTRINGS.ts
andi18n.translations = { en, ko };
add more languages insidei18n.translations
.import { getString } from '../../../STRINGS'; getString('LOGIN');
Copy sourcecode in /src/components/screen/Temp.tsx Copy sourcecode in /src/components/screen/test/Temp.test.tsx Create new tsx file with compnent name you will create
To do above more easily, you can simly install dooboo-cli. Then you can easily create [screen] or [shared] components along with test file
by running below commands.
# screen component
dooboo screen [MyScreen]
# shared component
dooboo shared [MyShared]
16.9
5
3