Welcome to the Flax GUI repo!
Flax GUI is written in TypeScript and uses Electron/React.
This monorepo consists of the following packages:
Package name | Description |
---|---|
api | JS/TS library to access the Flax Blockchain RPC |
api-react | React library that wraps api in hooks |
core | Common React components and hooks |
gui | The actual GUI package. It uses our packages like api-react and core under the hood |
icons | Flax specific icons |
wallets | Common React components and hooks. Do not use this in you project. Will be merged to core package soon |
- This repo (flax-blockchain-gui) must be under flax-blockchain repo. Please follow the installation steps for the flax-blockchain. Make sure to install from source code (git clone...).
- Run the
sh install-gui.sh
as instructed in the previous step. This will clone the flax-blockchain-gui under flax-blockchain repo. - Run
npm run dev:gui
When developing, please:
-
Only edit the code with the Vscode editor.
-
Always have flax-blockchain-gui opened as a root folder in the Vscode and not flax-blockchain, or flax-blockchain-gui/packages/... Failing to do so will result in incorrect auto linting and auto formatting which would not go trough the CI quality checks.
-
When you open the repo in the vscode, click on "Install recommended plugins" pop-up.
-
To develop in testnet, please follow these steps.
-
Please write tests for your code
-
When disabling an eslint rule, please provide a reason after two dashes (--), example:
// eslint-disable-next-line react-hooks/exhaustive-deps -- Some dependencies intentionally left out
To install an NPM package, please navigate to the root directory of this repo.
- To install
lodash
for all packages:npx lerna add lodash
- To install
lodash
for single package:npx lerna add lodash --scope=@flax-network/icons
- To install as a dev dependency, add
--dev
After adding a new NPM package, please pin down the package version. This is done to lower the possibility of supply chain attacks.
-
react/no-array-index-key
Only use
index
as akey
when all of the following conditions are met:- the list and items are static / hardcoded.
- the list is never reordered or filtered.
In all other cases, you have to figure out what unique string you will use as an
key
, or create a dedicatedID
.
- Git branch from "main"
- For Flax employees: prefix your branch with your name, like this:
yourName/what-is-the-code-about
. This helps when cleaning up old branches. - All commits must be signed.
-
Separate subject from body with a blank line
A single subject line is usually sufficient, but if you need to include additional details, add an empty line after the subject and enter the detailed message. Example:
Capitalized, short (70 chars or less) summary
More detailed explanatory text, if necessary. Wrap it to about 72 characters or so. In some contexts, the first line is treated as the subject of an email and the rest of the text as the body. The blank line separating the summary from the body is critical (unless you omit the body entirely); tools like rebase can get confused if you run the two together.
-
Commit subject line should always be able to complete the following sentence:
If applied, this commit will
your subject line here
Fixed bug with Y-> Fix bug in the contact formAdding new field of X-> Add new field - "discount code", in the order formMore fixes for broken stuff-> Fix broken responsive layout
Do not edit files directly in the repo, but instead please head over to our Crowdin project and add/edit translations there.
-
npm install
in the root directory does not install packages correctly (Or other Lerna issues)Please run
npx lerna clean -y && rm -rf node_modules && npm install && npx lerna bootstrap
-
npm run dev:gui
fails to start the app without providing a reason- In your command line, please go to the
flax-blockchain
directory (one level up) - Run
. ./activate
- Run
cd flax-blockchain-gui
- Run
npm run dev:gui
to start the app. - If still does not work, please open you process manager and kill all Flax / Python related processes.
- In your command line, please go to the
Please check out the wiki and FAQ for information on this project.