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.
20962 Commits
705 Branches
1179 Tags
2.0 GiB
 
 
 
 
 
Tag: Branch: Tree: 7e4fd5c416
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '7e4fd5c416'
${ noResults }
Rocket.Chat/client
History
Pierre Lehnen 7e4fd5c416
Removed typecast 		4 years ago
..
UIKit/hooks Chore: Prettier for us all (#24000) 4 years ago
components Removed typecast 4 years ago
contexts [FIX] Skip admin info in setup wizard for servers with admin registered (#24485) 4 years ago
hooks [FIX] Read receipts showing first messages of the room as read even if not read by everyone (#24508) 4 years ago
lib Avoid typecasts 4 years ago
methods Chore: Move `callbacks` to /lib (#23456) 4 years ago
polyfills Chore: Replace Blaze templates (#24165) 4 years ago
providers client 4 years ago
sidebar imports 4 years ago
startup client 4 years ago
templateHelpers Chore: Prettier for us all (#24000) 4 years ago
views Avoid typecasts 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 Depack: Use mainModule for root files (#13508) 7 years ago
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