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
gabriellsh d3511eac8a
fix: User roles showing on the message header after opening user card, but with "Show roles" setting/preference disabled (#37984)
4 months ago
..
apps fix: `UserAutoCompleteMultiple` not removing selected items (#37823) 5 months ago
cachedStores chore: Enforce stricter TypeScript directives (#37709) 5 months ago
components fix: User roles showing on the message header after opening user card, but with "Show roles" setting/preference disabled (#37984) 4 months ago
contexts chore!: remove omnichannel voip (#37689) 4 months ago
definitions chore: Purge and rename removed v1 files (#37912) 4 months ago
hooks feat: Move enhanced navigation out of feature preview (#37285) 4 months ago
lib chore!: remove omnichannel voip (#37689) 4 months ago
meteor chore!: Remove API_Use_REST_For_DDP_Calls setting (#32590) 4 months ago
navbar test: Replace `data-qa` by accessible locators (#36757) 4 months ago
portals regression: Split enhanced navigation and second sidebar (#36763) 8 months ago
providers chore!: remove omnichannel voip (#37689) 4 months ago
router chore: Add `getPreviousRouteName` to `RouterContext` (#37752) 5 months ago
sidebar test: Replace `data-qa` by accessible locators (#36757) 4 months ago
startup chore!: Remove MeetPage and webRTC (#36671) 4 months ago
stores chore: Invert store/collection injection (#37412) 6 months ago
stories chore: Use `FieldHint` instead of `FieldDescription` on create modals (#36909) 8 months ago
uikit/hooks feat: Implement Call History contextual bar inside rooms (#37773) 5 months ago
views test: remove homepage `data-qa` attributes (#38004) 4 months ago
README.md
importPackages.ts chore!: Remove MeetPage and webRTC (#36671) 4 months ago
main.ts chore!: remove `ecdh` (#37123) 4 months ago
serviceWorker.ts
ui.ts chore!: remove omnichannel voip (#37689) 4 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