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
Diego Sampaio 132814ac8f
[FIX] resumeToken not working (#23379)
4 years ago
..
UIKit/hooks [IMPROVE] Throw error if no appId is provided to useUIKitHandleAction (#23221) 4 years ago
components [FIX] Sidebar not closing when clicking in Home or Directory on mobile view (#23218) 4 years ago
contexts Regression: LDAP Issues (#23306) 4 years ago
hooks [NEW] Omnichannel source identification fields (#23090) 4 years ago
lib [NEW] Seats Cap (#23017) 4 years ago
methods Chore: Move client helpers (#23178) 4 years ago
polyfills
providers [BREAK] LDAP Refactoring (#23171) 4 years ago
sidebar [FIX] Sidebar not closing when clicking in Home or Directory on mobile view (#23218) 4 years ago
startup [FIX] resumeToken not working (#23379) 4 years ago
templateHelpers Chore: Move client helpers (#23178) 4 years ago
types Chore: Move client helpers (#23178) 4 years ago
views Regression: LDAP User Data Sync not always working (#23321) 4 years ago
.eslintrc.js Chore: Move client helpers (#23178) 4 years ago
.prettierrc
README.md
head.html
importPackages.ts [BREAK] LDAP Refactoring (#23171) 4 years ago
main.ts
templates.ts [FIX] Sidebar not closing when clicking in Home or Directory on mobile view (#23218) 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