The communications platform that puts data protection first.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
Rocket.Chat/client
gabriellsh 1acd18196a
Regression: Discussion room crashing (#24272)
3 years ago
..
UIKit/hooks Chore: Prettier for us all (#24000) 3 years ago
components [FIX] Fixing the changing custom status behavior (#24218) 3 years ago
contexts [IMPROVE] Setup Wizard Registration Flow (#23676) 3 years ago
hooks [IMPROVE] Show Channel Icons on Room Header & Info panels (#24239) 3 years ago
lib Merge branch 'master' into develop 3 years ago
methods Chore: Move `callbacks` to /lib (#23456) 3 years ago
polyfills Chore: Replace Blaze templates (#24165) 3 years ago
providers [IMPROVE] Setup Wizard Registration Flow (#23676) 3 years ago
sidebar [FIX] Fixing the changing custom status behavior (#24218) 3 years ago
startup [IMPROVE] Rewrite Omnichannel Queue Page to React(#24176) 3 years ago
templateHelpers Chore: Prettier for us all (#24000) 3 years ago
views Regression: Discussion room crashing (#24272) 3 years ago
.eslintrc.js Chore: Prettier for us all (#24000) 3 years ago
README.md Chore: Doc Client Readme (#21588) 4 years ago
head.html
importPackages.ts Chore: Replace Blaze templates (#24165) 3 years ago
main.ts
templates.ts Chore: Replace Blaze templates (#24165) 3 years ago

README.md

How does the folder structure work in the frontend?

The folder structure should follow rocketchat's html 'semantics' like:

    main   -> room
                -> header
                    ...
                -> contextualbar
                    roominfo
                        ...
            -> sidebar
                -> Header
                    -> search
                    -> actions
                        ...
                -> list
                    ...
                -> footer
                    ...

Each folder is composed by:

File
index.jsx
ContainerComponent.jsx
contexts (optional)
providers (optional)
components (optional)
hooks (optional)
libs (optional)

We strongly suggest that you start developing your components/hooks/libs inside the folder where they will be directly used. If you ever find that you will use them in more than one place, then you should "promote" the code to an upper level, where it can be commonly accessed by all others

we have being moving code from blaze to react, but sometimes we will need render under blaze enviroment, to do that use createTemplateForComponent