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.
27879 Commits
703 Branches
1177 Tags
2.1 GiB
 
 
 
 
 
Tag: Branch: Tree: 83eeed0a8c
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '83eeed0a8c'
${ noResults }
Rocket.Chat/apps/meteor/client
History
Tasso Evangelista 83eeed0a8c
chore: User presence relocation (#36704) 		5 months ago
..
NavBarV2 fix: create-c and create-p not being applied to Team Creation (#36592) 5 months ago
apps chore: Reorganizing cached stores (#36565) 5 months ago
cachedStores chore: Reorganizing cached stores (#36565) 5 months ago
components chore: Split connection status data among other contexts (#36712) 5 months ago
contexts
…
definitions chore: Internally operate Minimongo collections over Zustand stores (as transition for stores-only) (#35470) 7 months ago
hooks chore: Split connection status data among other contexts (#36712) 5 months ago
lib chore: User presence relocation (#36704) 5 months ago
meteorOverrides chore: Reorganizing cached stores (#36565) 5 months ago
omnichannel i18n: Remove some duplicated keys (#36690) 5 months ago
portals chore: Move shared `Modal` code to `ui-client` package (#36356) 6 months ago
providers chore: User presence relocation (#36704) 5 months ago
router chore: Fork client-side router decoupling it from Meteor APIs (#36602) 5 months ago
sidebar chore: Relocate client-side custom OAuth modules (#36673) 5 months ago
sidebarv2 chore: Remove unused code (#36453) 6 months ago
startup chore: User presence relocation (#36704) 5 months ago
stores chore: Reorganizing cached stores (#36565) 5 months ago
stories
…
uikit/hooks
…
views chore: Split connection status data among other contexts (#36712) 5 months ago
voip chore: Remove references to deprecated `Modal.*` components (#36396) 6 months ago
README.md
…
ecdh.ts
…
importPackages.ts chore: Relocate client-side custom OAuth modules (#36673) 5 months ago
main.ts chore: Fork client-side router decoupling it from Meteor APIs (#36602) 5 months ago
serviceWorker.ts
…
ui.ts feat: Separate video call and voice call room actions (#35700) 9 months 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