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
Tushar Grover dbe69aff8e
fix(ux): Show full channel name on hover (#38320)
2 days ago
..
apps fix: `UserAutoCompleteMultiple` not removing selected items (#37823) 2 months ago
cachedStores chore: Enforce stricter TypeScript directives (#37709) 3 months ago
components chore: replace messages `data-qa` (#38493) 2 days ago
contexts refactor: Phase-out async state API (#37944) 1 month ago
definitions chore: Purge and rename removed v1 files (#37912) 2 months ago
hooks chore: add missing abacAttributes to useRoomIcon Pick type (#38427) 3 weeks ago
lib regression: Codebock autoclose unclosed markdown code blocks on message send (#39007) 4 days ago
meteor chore: Move Github OAuth to `CustomOAuth` (#37604) 1 month ago
navbar fix: saving custom status without changes breaks the UI (#38186) 1 month ago
portals refactor(eslint): Enable `react/no-children-prop` (#38170) 1 month ago
providers feat: Add "Direct Message" button to Media Call widget (#38169) 1 month ago
router chore: Add `getPreviousRouteName` to `RouterContext` (#37752) 3 months ago
sidebar fix(ux): Show full channel name on hover (#38320) 2 days ago
startup chore!: Remove MeetPage and webRTC (#36671) 2 months ago
stores fix: Remove the delay of waiting on event on WS to consider a message sent (#38067) 2 months ago
stories refactor(eslint): Enable `react/no-children-prop` (#38170) 1 month ago
uikit/hooks feat: Implement Call History contextual bar inside rooms (#37773) 2 months ago
views chore: Incorrect validation message label for 'Post as' field (#39103) 2 days ago
README.md
importPackages.ts chore!: Remove MeetPage and webRTC (#36671) 2 months ago
main.ts chore!: remove `ecdh` (#37123) 2 months ago
serviceWorker.ts
ui.ts chore!: remove omnichannel voip (#37689) 2 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