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 94de04ef05
Chore: Fix return type warnings (#25275)
4 years ago
..
UIKit/hooks Chore: move definitions to packages (#25085) 4 years ago
components [FIX] Add katex render to new message react template (#25239) 4 years ago
contexts [FIX] Close room when dismiss wrap up call modal (#25056) 4 years ago
definitions Chore: move definitions to packages (#25085) 4 years ago
hooks Chore: move definitions to packages (#25085) 4 years ago
lib [FIX] Client disconnection on network loss (#25170) 4 years ago
methods
polyfills
providers [FIX] Client disconnection on network loss (#25170) 4 years ago
sidebar [FIX] Message preview not available for queued chats (#25092) 4 years ago
startup Chore: move definitions to packages (#25085) 4 years ago
stories Chore: move definitions to packages (#25085) 4 years ago
templateHelpers Chore: move definitions to packages (#25085) 4 years ago
views Chore: Fix return type warnings (#25275) 4 years ago
.eslintrc.js
README.md
head.html
importPackages.ts [NEW] Alpha Matrix Federation (#23688) 4 years ago
main.ts Chore: move definitions to packages (#25085) 4 years ago
templates.ts

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