mirror of
https://github.com/Unleash/unleash.git
synced 2024-12-22 19:07:54 +01:00
728477e238
* fix: setup new routes * fix: copy toggle * fix: link to correct project * fix: redirect oss to default * fix: update tests * fix: edit path * fix: remove invalid property * fix: add project to test data * fix: update paths to use features * fix: update test data * fix: update snapshots * fix: only show button to add toggle if you have access * fix: change heading * fix: use new route * fix: archive view * fix: update snapshots * fix: sorting headers * fix: list headers * fix: only show span if revive is present * fix: add border to list * fix: update snapshots * fix: remove console log |
||
---|---|---|
.. | ||
.github/workflows | ||
public | ||
src | ||
.editorconfig | ||
.gitignore | ||
.nvmrc | ||
.prettierignore | ||
.prettierrc | ||
CHANGELOG.md | ||
craco.config.js | ||
index.js | ||
LICENSE | ||
package.json | ||
README.md | ||
tsconfig.json | ||
typings.json | ||
vercel.json | ||
yarn.lock |
Developing
Why did you render
This application is set up with WDYR and craco in order to find, debug and remove uneccesary re-renders. This configuration can be found in /src/wdyr.ts.
In order to turn it on, change the configuration accordingly:
if (process.env.NODE_ENV === 'development') {
const whyDidYouRender = require('@welldone-software/why-did-you-render');
whyDidYouRender(React, {
trackAllPureComponents: true,
});
}
Now you should be able to review rendering information in the console. If you do utilise this functionality, please remember to set the configuration back to spare other developers the noise in the console.
Run with together with local unleash-api:
You need to first start the unleash-api on port 4242 before you can start working on unleash-frontend. Start webpack-dev-server with hot-reload:
cd ~/unleash-frontend
npm install
npm run start
Run with heroku hosted unleash-api:
cd ~/unleash-frontend
npm install
npm run start:heroku
UI Framework
We are using material-ui.
Happy coding!