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
eduardofcabrera 0192e7e983
[IMPROVE] ChatBox Text to File Description (#24451)
4 years ago
..
UIKit/hooks Chore: Prettier for us all (#24000) 4 years ago
components [IMPROVE] Close modal on esc and outside click (#24275) 4 years ago
contexts [IMPROVE] Setup Wizard Registration Flow (#23676) 4 years ago
hooks [IMPROVE] Show Channel Icons on Room Header & Info panels (#24239) 4 years ago
lib [FIX] OAuth mismatch redirect_uri error (#24450) 4 years ago
methods Chore: Move `callbacks` to /lib (#23456) 4 years ago
polyfills Chore: Replace Blaze templates (#24165) 4 years ago
providers [IMPROVE] Close modal on esc and outside click (#24275) 4 years ago
sidebar [FIX] Fixing the changing custom status behavior (#24218) 4 years ago
startup [FIX] Add ?close to OAuth callback url (#24381) 4 years ago
templateHelpers Chore: Prettier for us all (#24000) 4 years ago
views [IMPROVE] ChatBox Text to File Description (#24451) 4 years ago
.eslintrc.js Chore: Prettier for us all (#24000) 4 years ago
README.md Chore: Doc Client Readme (#21588) 5 years ago
head.html
importPackages.ts Chore: Replace Blaze templates (#24165) 4 years ago
main.ts [FIX] OAuth mismatch redirect_uri error (#24450) 4 years ago
templates.ts Chore: Replace Blaze templates (#24165) 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