apitech
/
Rocket.Chat
mirror of https://github.com/RocketChat/Rocket.Chat
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
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.
20826 Commits
720 Branches
1191 Tags
2.1 GiB
 
 
 
 
 
Tag: Branch: Tree: f92db4fa59
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'f92db4fa59'
${ noResults }
Rocket.Chat/client
History
Diego Sampaio 775584f181
Merge branch 'master' into develop 		4 years ago
..
UIKit/hooks Chore: Prettier for us all (#24000) 4 years ago
components feat: enabling emoji on custom status (#24170) 4 years ago
contexts [FIX] Integration section crashing opening in My Account (#24068) 4 years ago
hooks Chore: Replace Blaze templates (#24165) 4 years ago
lib Merge branch 'master' into develop 4 years ago
methods Chore: Move `callbacks` to /lib (#23456) 4 years ago
polyfills Chore: Replace Blaze templates (#24165) 4 years ago
providers Chore: Move `callbacks` to /lib (#23456) 4 years ago
sidebar feat: enabling emoji on custom status (#24170) 4 years ago
startup Merge branch 'master' into develop 4 years ago
templateHelpers Chore: Prettier for us all (#24000) 4 years ago
views [FIX] Integration section crashing opening in My Account (#24068) 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 [NEW][Enterprise] Second layer encryption for data transport (alpha) (#21692) 5 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