If you are a developer and are thinking about contributing to the project, read this guide.
git checkout master
npm install
npm run dev
With yarn:
yarn
yarn dev
- The use of custom
TailwindCSS
variables is only for extremely special cases. - If the created component is not a smart component, add it to the
storybook
to view it. - It should always be separated with a white line between labels. As shown in the following code, a space between
element-1
andelement-2
<div class="container">
<div class="element-1" />
<div class="element-2" />
</div>
- You must also separate with white lines in case a variable or action breaks into 2 lines or more.
adminAndModerators
is a variable whose action is divided into 2 lines, therefore it is separated from the variables above with a white line
const users = [users...]
const timestamp = Date.now()
const adminAndModerators = process.filter(user => user.isAdmin || user.isModerator)
- The
hooks
: Newhooks
are only created if they are to be reused in multiple places or if the complexity level of ahook
is very large. - The use of
context
(in this case withzustand
) is dedicated to special cases only. - Subscription to
matrix events
is done using the created hookuseEventListener
, for example:
useEventListener(RoomMemberEvent.Typing, (_event, member) => {})
When the components are not intelligent, we use a storybook
to preview these components.
To write a preview of a component, create a new file in the path src/stories
with the name yourComponent.stories.tsx
of example.
✨ To facilitate the process we have a template
with which you can quickly create a code for a storybook
.
🔍To see the previews created in the storybook you must do:
yarn storybook
Or its equivalent in npm
.
- Title of what you did.
- List of things you did
- Photo (optional)
📄 We have a pull request template here pull_request_template
In the way of writing PR Commit we use English
and commitlint
for the style. For example:
feat: Implement useDebounced
hook
For more information on the use of commitlint see here