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
Douglas Fabris e24af45c8c
chore: Replace `useForm` in favor of RHF on Omnichannel Triggers (#30776)
2 years ago
..
components chore: Replace `useForm` in favor of RHF on Omnichannel Triggers (#30776) 2 years ago
contexts feat: Omnichannel MAC limitations (#30463) 2 years ago
definitions feat: add supported versions + minimum clients versions to the info endpoint (#30178) 2 years ago
hooks feat: workspace info admin page (#30434) 2 years ago
lib feat: workspace info admin page (#30434) 2 years ago
methods
navbar chore: use pixels for margins and paddings (#30023) 2 years ago
polyfills refactor(uikit): uikit interactions (#30534) 2 years ago
portals
providers chore: Remove custom sounds meteor.startup (#30659) 2 years ago
sidebar feat: subscription page (#30551) 2 years ago
startup feat: Deployment Fingerprint (#30411) 2 years ago
stories fix: Login page language switcher (#30106) 2 years ago
uikit/hooks refactor(uikit): Reshape UiKit context value (#30073) 2 years ago
views chore: Replace `useForm` in favor of RHF on Omnichannel Triggers (#30776) 2 years ago
README.md
importPackages.ts chore: split fuselage js/css (#30039) 2 years ago
main.ts refactor(client): async loading (#30314) 2 years ago
ui.ts refactor: `RoomToolboxContext` redesign (#29982) 2 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