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/apps/meteor/client
Kevin Aleman aaad1dd9d8 fix: `onlyAvailable` property wrong type (#30748) 2 years ago
..
UIKit/hooks refactor: UiKit surfaces and related stuff (#29955) 3 years ago
components fix: `onlyAvailable` property wrong type (#30748) 2 years ago
contexts fix: rejected conference calls continue to ring (#30143) 2 years ago
definitions
hooks fix: Sync Omnichannel changes on 6.4.3 (#30729) 2 years ago
lib refactor(client): async loading (#30314) 2 years ago
methods refactor: create i18n package (#29097) 3 years ago
navbar chore: use pixels for margins and paddings (#30023) 3 years ago
polyfills refactor(client): async loading (#30314) 2 years ago
portals
providers fix: Private apps list infinite loading in air-gapped environments (#30775) 2 years ago
sidebar fix: user dropdown menu position on RTL layout (#30490) 2 years ago
startup feat: message menu sections with dividers (#30116) 2 years ago
stories fix: Login page language switcher (#30106) 2 years ago
views fix: Private apps list infinite loading in air-gapped environments (#30775) 2 years ago
README.md
importPackages.ts chore: split fuselage js/css (#30039) 3 years ago
main.ts refactor(client): async loading (#30314) 2 years ago
ui.ts refactor: `RoomToolboxContext` redesign (#29982) 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