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
Guilherme Gazzo 9932771f64
[FIX] Custom script not being fired (#24901)
4 years ago
..
UIKit/hooks Chore: Prettier for us all (#24000) 4 years ago
components [FIX] Show only enabled departments on forward (#24829) 4 years ago
contexts Chore: converted more hooks to typescript (#24628) 4 years ago
hooks Chore: converted more hooks to typescript (#24628) 4 years ago
lib [FIX] Disable voip button when call is in progress (#24864) 4 years ago
methods Chore: converted more hooks to typescript (#24628) 4 years ago
polyfills Chore: Replace Blaze templates (#24165) 4 years ago
providers [FIX] Missing dependency on useEffect at CallProvider (#24882) 4 years ago
sidebar [FIX] Disable voip button when call is in progress (#24864) 4 years ago
startup Chore: Convert server functions from javascript to typescript (#24384) 4 years ago
templateHelpers Chore: Prettier for us all (#24000) 4 years ago
views [FIX] Custom script not being fired (#24901) 4 years ago
.eslintrc.js Chore: Prettier for us all (#24000) 4 years ago
README.md
head.html
importPackages.ts [FIX] Apple OAuth (#24879) 4 years ago
main.ts [FIX] OAuth mismatch redirect_uri error (#24450) 4 years ago
templates.ts [FIX] Apple OAuth (#24879) 4 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