The Onyx protocol interface is currently being redesigned. At the moment our priorities are refactoring and completing the new site design. We can't guarantee a timely response to unsolicited pull requests that are not on our roadmap.

Install make and husky globally:

npm i make -g && npm i husky -g && husky install

Install dependencies

yarn

Prepare local environment:

cp .env.template .env

You’ll need to have Node >16 or later version on your local development machine

To deploy, raise a PR to update image and config at: https://github.com/OnyxProtocol/onyx-k8s-app

To run local development:

yarn start

To run local storybook:

yarn storybook

To run dev environment:

docker compose up onyx-ui-dev

To run prod environment:

docker compose build && docker compose up onyx-ui-prod

Tests run in CI on push using Github actions. They are all required to pass.

Types are checked by running tsc.

We are enforcing code styles using eslint, prettier and stylelint.

Visual regressions tests are run by snapshoting storybooks and running diffs against the previous baseline and the new snapshots. A unique story is required to test visual regressions on different prop variations.

If regressions are detected or a new story is added on a PR a review is required after the last commit is pushed. If a new commit is pushed after the PR is approved, it will reset the approval for the new baseline and a new review will be required in order for it to be accepted.

We use i18next to translate the app. All the translations are stored inside src/assets/translation. This means all texts within the app need to be rendered using the t function, returned by useTranslation:

import { useTranslation } from 'translation';

const Component: React.FC = () => {
  const { t } = useTranslation();

  return <>{t('componentName.textKey')}</>;
};

If a text contains HTML or JSX elements, then the Trans component can be used instead:

import { useTranslation } from 'translation';

const Component: React.FC = () => {
  const { Trans } = useTranslation();

  return (
    <Trans i18nKey="componentName.textKey" components={{ Anchor: <a href="https://acme.com" /> }} />
  );
};

If a text needs to be accessed from outside of a component, then the t function exported by the translation client can be used:

import { t } from 'translation';

const myFunction () => t('functionName.textKey');

Note that this should only be used in cases where we can't use useTranslation. The hook does extra processing, hence why it is preferred in all other cases.

After adding internationalized texts within the app using the methods described, you'll need to extract the translation keys from the code using the next command:

yarn extract-translation-keys

The new translations will be added to the relevant translation file (e.g.: src/assets/translation/en.json) with a default text, which you'll need to update with the content you want.

We use TypeChain to automatically generate types for our contracts, using their ABIs located at src/constants/contracts/abis.

Note that the types aren't committed to the repo, since they are rebuilt every time TypeChain generates them. Instead, they are automatically generated upon installing dependencies. You will find them at src/types/contracts.