The communications platform that puts data protection first.

hacktoberfest collaboration foss javascript meteor real-time webrtc mit slack chat free

History

Júlia Jaeger Foresti 1a973719d8 chore: delete `Sidebar` unused files (#38529 )		2 days ago
..
apps	…
cachedStores	…
components	fix: `UserAutoCompleteMultiple` not considering `UI_Use_Real_name` setting (#38299 )	4 days ago
contexts	refactor: Phase-out async state API (#37944 )	3 weeks ago
definitions	chore: Purge and rename removed v1 files (#37912 )	2 months ago
hooks	fix: slash command list is incomplete during startup (#38267 )	3 weeks ago
lib	fix: Sidebar message preview showing "undefined" (#38262 )	4 days ago
meteor	chore: Move Github OAuth to `CustomOAuth` (#37604 )	3 weeks ago
navbar	fix: saving custom status without changes breaks the UI (#38186 )	4 weeks ago
portals	refactor(eslint): Enable `react/no-children-prop` (#38170 )	3 weeks ago
providers	feat: Add "Direct Message" button to Media Call widget (#38169 )	3 weeks ago
router	…
sidebar	chore: delete `Sidebar` unused files (#38529 )	2 days ago
startup	…
stores	fix: Remove the delay of waiting on event on WS to consider a message sent (#38067 )	1 month ago
stories	refactor(eslint): Enable `react/no-children-prop` (#38170 )	3 weeks ago
uikit/hooks	…
views	fix: Sidebar message preview showing "undefined" (#38262 )	4 days ago
README.md	…
importPackages.ts	…
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